| Great story. I think this is the same reason Microsoft Office is so popular when there usually are "better" alternatives. Because Word is like pen and paper with spell check. You can add whatever shit you want wherever you want with zero effort. But you don't realize the technical debt you will have to pay for later because nothing is consistent, diffing is a nightmare and your data is everything but normalized. Want a header, just increase the fontsize, Is that really a header?
"Hmm, it's thick and big, whatever, did anyone say lunchbreak?" Save exit. For small temporary documents like party-invitations this is fine, doing anything else would be silly. But companies actually use word for serious documents like 100+ pages technical specifications valid for years with tons of versions of each document. It is scary how much mission critical information that is stored in this form, at one of my previous jobs if changes happened outside our division, every document depending on this data had to be updated by hand because it's just plain text in word, nothing is connected or autogenerated. It's grunt work but it actually gets the job done sooner or later. I've seen this in several places. Word and excel keeps the world spinning even though it at the same time requires much more manpower than is reasonable. Someone has to make an alternative to word that is as easy to use but doesn't allow you to do all the stupid stuff. Enforce styles, make references and other data-connections easy, smooth and reliable and provide a good diff. I think this is one of the greatest challenges in software development, allow freedom at the same time as you have a strict data model that can be analyzed, processed and generated by a program. Something that paper will always beat, regardless of what kind of paper you get you can always write and highlight on it, with software that is very exceptional. |
Notepad? Vim? Plus a little bit of Markdown?
I had to do a big certification project. A guy went on with a MS project massive file on my team with milestones, completion percentages and so on. I couldn't see it without nausea (and obviously I couldn't see it at all on my Linux box), so I dumped it as text, reformatted it with some Mardown and custom markup, and did a little parser highlighter in a week-end. Then I could put this under version control, have meaningful commits and diffs, and the MS project guy stopped trying to micro-manage my team, and was fired eventually...
That is to say that for me (but not for everyone, I am aware of that issue) nothing beats plain text and, when needed, some markup. Exceptions could be printed books and magazines. But I would not trust MS Word with a 500 pages specification document, and more so because it is important and long, and must be precise. As far as I can tell, TCP/IP specs are written in pure text with some markup.