4 ms·
nah. documentation only goes so far. you handle this by having and exercising a disaster recovery plan and having (and listening to) competent people that woul
by rantwasp 6y ago
nah. documentation only goes so far.
you handle this by having and exercising a disaster recovery plan and having (and listening to) competent people that would spot this issue in a jiffy.
- foobiekr 6y agoThis. I actually think just documentation is, well not completely worthless but close to. Imagine telling someone they could learn to weld airframes by reading. Just no.
- twobitshifter 6y agoFor software, it’s the maintenance task that’s helped by documentation not building. They still need to know how to build but it’s a lot easier with documentation. I know that when we use software packages we all rely on the documentation to understand how to use it and code our desired behaviors. It’s obvious that our own code can benefit from documentation in the same way.
- rantwasp 6y agodocumentation is required but not sufficient. also, documentation is usually outdated really fast if the person maintaining the system leaves and/or does not care