4 ms·
I totally agree. When I write documentation. I'm often at a point where I ask myself: do I document this small inconsistency/inconvenience, or do I just remove
by perlgeek 6y ago
I totally agree.
When I write documentation. I'm often at a point where I ask myself: do I document this small inconsistency/inconvenience, or do I just remove/fix it?
Often enough it's easier to make things more consistent than both documenting the inconsistency and getting people to read the docs and stop asking about it.
- mark-r 6y agoI remember well one time long ago when I did that. I had done the firmware for a piece of hardware that had some DIP switches to configure. I was having trouble doing the documentation for what each switch did and when you would want to configure it a particular way. Finally I realized it was because the switches weren't laid out logically, so I wrote the documentation the way I thought it should work then changed the code to match the documentation. Win-win, easier documentation and easier to use hardware.