That wasn't my take. Good documentation doesn't equate bureaucracy.
20 years ago, Spolsky wrote a blog post about how good documentation need not be unreadably dry and soulless. [0] From which:
> Rule 1: Be Funny
> Yep, rule number one in tricking people into reading your spec is to make the experience enjoyable.
[...]
> if you work in a company where people will respect you less because your specs are breezy, funny, and enjoyable to read, then go find another company to work for, because life is just too damn short to spend your daylight hours in such a stern and miserable place.
I'm not sure I'd go quite that far - it seems a bit much to leave an otherwise agreeable position just because they insist on humourless documentation - but I think he makes some important points.
