Recent searches
Search options
@bookwar@fosstodon.orgThe hardest part in writing docs is that you start describing things as is, then you see so many places the "as is" state needs improvement, so you run to fix that before documenting.
And since "as is" state is never perfect, you never finish the doc you have started.
Ⓐ @bookwar Yeah, it takes some willpower to suppress the need to fix things. Sometimes I write a "planned doc" separately that is the same doc but like the fixes already had been implemented. Just to allow myself to continue working on the doc and don't switch to codding until the current docs are finished.
@lig @bookwar It's so hard not to stop what you're doing to go fix random stuff. I think the best place to document the need for improvements is on the issue tracker. Writing docs becomes a loop of:
write doc;
write issue;
Which is all part of the "writing docs" task. You end up with a lot of new issues, then you can estimate effort and prioritize.
When you stop what you're doing to do something else, it becomes hard to plan. You can end up doing low-value work before the more urgent tasks.
