kuro5hin.org || HOWTO: write bad documentation that looks good

There is currently a great satire piece on kuro5hin.org describing how to write bad documentation that looks good. The best piece is towards the end when the author talks about trouble ticket systems.

Theoretically, your trouble ticket system contains all the information you've been trying to obfuscate. In practice, all such systems exemplify the flaws we've discussed: poor organization, too much irrelevant detail and too little discussion of 'why'. At best, your trouble ticket database is full of sketchy problem descriptions and meaninglessly vague resolution fields. More likely, the ticket database is an incoherent work of speculative fiction that doesn't contain records for many changes.