3 ms·
Right. Those developers who were given days and months to document their work deliberately did nothing instead. Wait, no, I've literally NEVER heard of manage
by Ensorceled 8y ago
Right. Those developers who were given days and months to document their work deliberately did nothing instead.
Wait, no, I've literally NEVER heard of management asking developers to delay the next release to document their work.
- bitwize 8y agoCouldn't they just find the time to document while they're developing? Oh, but they can't increase the estimate. The customer signed off on that estimate, so we're committed to deliver by that deadline.
- bigmanwalter 8y agoNot really. Code needs to solidify before you document it. Documentation is best saved for after a major release.
- Ensorceled 8y agoExactly. I'm always surprised when people think that it's easy to find time for documentation and that you only skipped that step because you are lazy and/or unprofessional.
- repolfx 8y agoHonestly, I know that's the conventional wisdom, but I've never once heard an engineer go to their manager and say, "I'd like to spend some time documenting this important process you asked me to implement" and being told "no, we don't have time to document! just keep it all in your head!" I'm sure this literally never happens. What I do see quite frequently is developers who don't like writing documentation finding ways to not do it or justify doing a poor job.
- arethuza 8y agoOnly time I've encountered a desperate fixation by a CIO on documenting applications was when the relevant development team was about to be laid off. Fortunately I had already resigned at that point.