How to build a documentation portfolio

You can start with a funny (to you) “how to write a how-to how-to”, but you better get serious soon!

Writing a pseudo-philosophical mini-essay about what requires documentation may get you one step closer to doing actual documentation work, but only because you yourself need these steps to get there!

Your articles about useful ruby tools are also useful steps, as you’re progressively getting the hang of addressing someone to talk about technical things. But I presume that you’ll need to get yourself, the first person singular, out of the equation before you start playing in the right ball park. Blogs have a function too. Documentation shall be more, if not entirely, impersonal.

(to be continued)

(updated after MicroCeph how-to)

Indeed, now that I’ve written something for a user who is not interested in me, but in making their project work, my screen is full of second person singular—and not the self-addressing one that I was using above, but really addressing the reader (which, by the way, is a pretty fun thing to do, but not easy to sustain, in fiction!)