@scottalanmiller said in Over documentation:
@Minion-Queen said in Over documentation:
The idea of creating the document to help you build out your documentation in theory should be a one time thing... As the management side of things I would say that there is hardly ever a case where too much documentation is an issue. All documentation should be done on the theory of "what if I get hit by a bus today?" can someone else step into my position seamlessly and the client not see any lag?
Too much documentation, though, can result in people being unable to find what is needed and the time needed to maintain it can become a point of inefficiency. And the more that there is, the more likely that it will go out of date and become a negative rather than a positive. Only good documentation is useful, and the more documentation you have, the higher chances that some of it will not be maintained.
We had an old guy that would "document" everything. He had tons of binders full of stuff and his home directory was huge with "documentation." His documentation was he would make a tiny note and then run a command and copy the output. That's pretty much all his notes were spanning back to ~2004-2005. He left and we ended up throwing it all away because we couldn't find anything useful at all.
