3 ms·
*cough* Thunderbird *cough*. In an ideal world, developers write documentation as they're developing. This seems to work really well for OpenBSD and its variou
by elric 3y ago
*cough* Thunderbird *cough*.
In an ideal world, developers write documentation as they're developing. This seems to work really well for OpenBSD and its various project, all of which have some of the best man pages out there.
- NoboruWataya 3y agoIMO it works a lot better for software that is aimed at other developers. Writing documentation that is accessible to non-technical users is a different skill.
- red-iron-pine 3y agodoesn't even have to be non-technical, just something not normally in your domain. a lot of documentation is put together as part of some KT handoff, and is written by technical folks in that domain, for folks in that domain.
- zilti 3y agoAll BSDs really, and I also want to mention GNU projects, they enforce this well, too. I made contributions to org-mode, and they made it clear that they won't accept a line of code without accompanying tests and, if applicable, handbook adjustments.