3 ms·
> Docs should tell a story when you can Depending on what the author means here, then please don't. I cannot work with documentation that attempt to convey tec
by mrweasel 3y ago
> Docs should tell a story when you can
Depending on what the author means here, then please don't. I cannot work with documentation that attempt to convey technical information using a cute story. I don't care about Jim who's trying run a porn site, I just need to know how to configure mod_rewrite.
That's also why I could not get through "why's (poignant) Guide to Ruby", it might be the best thing ever written but I don't care for the fiction wrapper, it's distracting.
- jzb 3y agoTo each their own. One person's tedious or distracting is just what other people need to succeed. (Source: I cannot stand watching videos when something can be conveyed via text. Nevertheless, that seems to be the way of the world these days. And I know folks who won't read anything if it could be a video instead. So it goes.)
- mrweasel 3y ago> I cannot stand watching videos when something can be conveyed via text I'm with you on that one, sadly YouTube pays better than your own blog.
- twodave 3y agoI’m with you. Docs need to provide 2 things: the reference and specific examples. That’s it. Tell me what all the options are and what they do, then show me usage of as much realistic possibilities as possible.