I recently gave a workshop about technical writing at Virtual RubyConf 2020. I enjoyed doing that tremendously, because, in case it’s not clear, I could yammer on forever about technical writing in much the same way as I normally yammer on about code, just to a smaller audience. I didn’t get to some of my outline in the workshop, so I’m being a little indulgent and writing it up here. I hope it’s helpful.
I will grant that I am very much not the market here, but if I’m being super nitpicky, there are five things I want from a writing tool for my technical writing: It is okay with proportional fonts. I don’t like my prose to look like code, which I realize is irrational. It should syntax color Markdown, including the backtick for code literals. It doesn’t go berserk when HTML or other symbols are inserted into the Markdown.
The end of the repair story At the end, a very positive experience with Apple support. The repair was free, done when they said it would be done, and all told, I spent less than fifteen minutes in the store between both halves of the visit. Plus, they replaced the top part of my pre-unibody MacBook, which was worn down and discolored from my gunky hands, almost as though they didn’t want an ugly Mac in the field.