2 ms·
I've made it a side-mission of mine to convince journalists to work in plaintext as much as possible. For all the concern of novices being intimidated by plaint
by danso 10y ago
I've made it a side-mission of mine to convince journalists to work in plaintext as much as possible. For all the concern of novices being intimidated by plaintext and code (plaintext basically is code as far as most laypeople is concerned), GUI-heavy software and rich text exact their own cognitive toll, not just in the form of having to keep up with interface upgrades (I've yet to move from Office 2011 to 2016), but in the way the user has to be trained to memorize the quirks of how the software modifies the data.
Excel is the obvious example here, e.g. zero-padded unique ids `00011` becoming `11`, dates turning into numbers like `41566`, and that's before you get into the madness that comes when trying to import/export data (think Mac-style line-endings into QGIS into Mac OSX Office, etc.).
At some point, it's just easier to take some time and be comfortable with the idea that things can be represented in plaintext. That data doesn't magically become data because software is used to open it. I've spent a good amount of time having to convince people that that CSV text file I sent them is not just random gibberish (trying to figure out how people's systems are set up to open certain files upon double-clicking is also not fun).
The inability to understand how software and data (human-readable plaintext or otherwise) can be separated is not limited to the humanities majors. Here's a case in which a civil engineer convinced the Ohio Supreme Court that using Esri ArcGIS inextricably tied the software to the (publicly-funded) GIS data, meaning that any member of the public who wants a copy of geospatial data in a form other than printed map will have to cough up an extra $2,000: http://spatiallyadjusted.com/use-esri-gis-and-your-data-becomes-inextricably-intertwined/ http://spatiallyadjusted.com/use-esri-gis-and-your-data-beco...