[[Knowledge Management]], [[Reproducible [[Social [[Science]]]]]], and [[Academic Workflow]]s – 100 Tweets for @threadapalooza 2020, let's go
#roamcult #𐃏
1/100

Pandoc is a magical piece of software, and if you're not using it for your academic writing you're missing out. Compile (basically) any document format to (basically) any other document format.
2/100
While Pandoc is fantastic, it's a bit like ffmpeg: extremely powerful, but without GUI apps too few people will use it. ffmpeg has a ton of GUI apps that basically just wrap the CLI, Pandoc doesn't have enough of them.
3/100
Citekeys + CSL files + Pandoc can easily cut ~10+ hours from your writing workflow. Citekeys come from LaTeX-Land, you can use them through Pandoc with anything. And CSL files make it super easy to switch citation styles.
4/100
Since many journals have their own version of popular formats, every journal should be required to publish a CSL file, LaTeX and Word Pandoc template ready for submission. I don't want to think about the collective hours wasted formatting stuff for submission.
5/100
Why Pandoc you ask? The one true document format are text files. Lindy effect - they've been around from the beginning, they will be around until the end. Everything else can be created from them – so write your stuff in text files, then use Pandoc.
6/100
"That contradicts your devotion to @RoamResearch!" Yeah, no. If Roam had shitty plain-text export like Evernote, sure. But I can get stuff easily as Markdown (plain text), so I lose nothing and gain a world of features. Use Roam, export to Markdown, publish w/ Pandoc.
7/100
Citekeys are powerful because they are unique ids for whole papers. And unlike DOIs they are _memorable_. citekey:doi = domain:ip
Think in terms of Roam, papers should have unique IDs for paragraphs, so I can do einstein1905movement/ASDJKSL to link to a specific paragraph
8/100
PDFs are a horrible format and should die in a fire. I don't know enough about document formats, but I know there are better ones out there that give the illusion of "uneditable" and that PDFs suck. But Lindy strikes again: we're stuck with them, I fear.
9/100
Talking about "permanence", I feel there's a lot of tension to be resolved around the question of "what do we actually know right now in this particular subfield"? The more we move to pre-prints and "public peer review", the less legible fields become, bc volume increases.
10/100
At least in the social sciences, there is way to much emphasis on "contributing to theory". I've received and seen others receive too much feedback along the lines of "this doesn't contribute much to theory". We need to falsify more, not introduce endless mods to theory.
11/100
Fun paper on that from International Relations
https://t.co/nZEKyxKGdq
12/100

More from Software

Kubernetes vs Serverless offerings

Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?

Well, let's try to look at both approaches and draw our own conclusions!

🧵⏬

1️⃣ A quick look at Kubernetes

Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.

There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you:
https://t.co/nuH4dmpUmf), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.

After all that, you need to write specs which instruct Kubernetes what the desired state of your application is, and finally let Kubernetes do its work. It's certainly not a NoOps platform, as you'll still need people knowing what they do and how to handle Kubernetes.



2️⃣ A quick look at (some!) serverless offerings

The offer is pretty simple: You write the code, the platform handles everything else for you. It's basically leaning far to the NoOps side. There is not much to manage anymore.

Take your Next.js / Nuxt.js app, point the ...
🚨 🦮 Seven ways to test for accessibility using only what is already in browser developer tools of Chromium browsers https://t.co/C7kdbigHGE

@MSEdgeDev @EdgeDevTools @ChromiumDev
#tools #accessibility #browsers
Also, a thread: 👇🏼


Issues pane, powered by @webhintio, listing accessibility issues with explanations why these are problems, links to more info and direct links to the tools where to fix the problem.
https://t.co/4K5RynHhbg


The inspect element overlay showing accessibility relevant information of the element, including contrast information, ARIA name, role and if it can be focused via keyboard.


Colour picker with contrast information offering colours that are AA/AAA compliant. You can also see compliant colours indicated by a line on the colour patch.
Note: the current algorithm fails to take font weight into consideration, that's why there will be a new one.


Vision deficit ("colour blindness") emulation. You can see what your product looks like for different visitors.
https://t.co/bxj1vySCAb

You May Also Like