Most documentation tends to suffer the same problem as most of the code it's written about, i.e. over complicated, verbose and full of unnecessary crap.
There's also the problem that some developers (and managers who used to be developers) have the opinion that any time spent not coding is time wasted
Then there are also companies with ridiculous documentation templates which need to be followed at all times and bloat what could be a 1 page diagram with a bit of text to 10 pages with an abstract, introduction, intended audience, distribution lists, contents page etc...
There are some good wiki systems which can be used on the corporate system which are a much better idea than hundreds of word documents. The beauty of the wiki pages is that high level docs can easily link to lower level technical explanations meaning that a reader only needs to dig as deep as they need to.
There's also the problem that some developers (and managers who used to be developers) have the opinion that any time spent not coding is time wasted
Then there are also companies with ridiculous documentation templates which need to be followed at all times and bloat what could be a 1 page diagram with a bit of text to 10 pages with an abstract, introduction, intended audience, distribution lists, contents page etc...
There are some good wiki systems which can be used on the corporate system which are a much better idea than hundreds of word documents. The beauty of the wiki pages is that high level docs can easily link to lower level technical explanations meaning that a reader only needs to dig as deep as they need to.
Comment