Plain Text, Papers, Pandoc

Plain Text, Papers, Pandoc:

In the Engineering model, meanwhile, plain text files are at the center of your work. The most “real” thing in your project will either be those files or, more likely, the Git, Mercurial, or SVN repository that controls the project. Changes are tracked outside the files. Data analysis is managed in code that produces outputs in (ideally) a known and reproducible manner. Citation and reference management will likely also be done in plain text, as with a BibTeX .bib file. Final outputs are assembled from the plain text and turned to .tex, .html, or .pdf using some kind of typesetting or conversion tool. Very often, because of some unavoidable facts about the world, the final output of this kind of solution is also a .docx file.

Academic Markdown and Citations

Academic Markdown and Citations · Chris Krycho:

The idea of plain-text solutions to academic writing is not especially new; only the application of Markdown to it is — and that, only relatively. People have been doing this, and documenting their approaches, for quite a while. Moreover, tools for managing references and citations have existed for quite some time as well; the entire LATEX toolchain is largely driven by the concerns of academic publishing, and as such there are tools in the LATEX ecosystem which address many of these problems.2

Citations in Scholarly Markdown

Citations in Scholarly Markdown:

Citations of the scholarly literature are an essential part of scholarly texts and therefore have to be supported by scholarly markdown. Both the Pandoc and Multimarkdown flavors of markdown support citations, using a bibtex file that contains citations, placeholders for citekeys – [@smith04] for Pandoc and [#smith04] for Multimarkdown – and the Citation Style Language for citation formatting (Pandoc). A very reasonable approach would therefore be to use this functionality, with a preference for Pandoc because of the Citation Style Language support. All reference managers can export to the bibtex format, and some of them (e.g. Papers) make it very easy to copy and paste citekeys.

The Story of MACOS

The Story of MACOS: How getting curriculum development wrong cost the nation, and how we should do it better | Computing Education Research Blog:

By 1971, Dow realizes that the controversies around MACOS could easily have been avoided. They had made choices in their materials that highlighted the challenges of Eskimo life graphically, but the gory details weren’t really necessary to the learning objectives. They simply hadn’t thought enough about their users, which included the teachers, administrators, parents, and state education departments.

I believe in the IndieWeb. It needs to believe in itself

Fogknife : I believe in the IndieWeb. It needs to believe in itself.:

When Twitter announced its plans to start asphyxiating all extant third-party clients this summer, I decided I would never again let my heart get broken by a web-identity service that invites me to invest so much of myself without offering matching levels of ownership and control. I have grown utterly weary of the every-few-years trudge of picking whatever service seems most agreeable at the moment, building up my network once again, and then enjoying things for a time while waiting for the rot to set in after management shifts and shareholders start grumbling.

Photographer turns bullied kids into Avengers

Photographer turns bullied kids into Avengers in this empowering project – DIY Photography:

We’ve seen photographer Josh Rossi turn kids into superheroes before. When his three-year-old daughter received hateful comments after he photographed her as Wonder Woman, the photographer decided to use his creativity to send a message against bullying. He gathered fifteen kids who have been bullied and turned them into Avengers for a photo shoot.