NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Documentation (Score:1)
I've always felt that taking an inverse Russian Doll approach to documentation would be much more beneficial for the end user (if they actually ended up reading docs of course ). By this I mean have a series of progressively larger documents to describe the application/process.
Start off with a 5-10 page overview of sub-systems/architecure/relationships/work-flow. For the next document for each page in the preceeding document have 5-10 more pages. Repeat until the final document has the level of granularity needed.
In conjuction there should be a straight reference document and a cookbook document. All documents should be crosslinked so that if I read the initial 5-10 page doc any concept would link me to several varying levels of granularity as well as examples (cookbook) and mechanics (i.e. api's within the technical reference).
I realize that the resources needed to maintain this would be large but I wonder how much would be recouped in decreased support cost.
None of this is very related to the journal entry but it came to mind since I've been spending a couple of agonizing weeks working with Merant VM documentation (thousands of pages). Thousands of pages of documentation and anything I really want to know can't be found.
Reply to This
Re:Documentation (Score:1)
This applies to grammar of natural languages too, I think.