TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
No commentary to that extent is "right" or "wrong". Parts I'll agree
with and parts I won't. Example:
1) "Wait. Delay the creation of all documents as late as possible,
creating them just before you need them. For example, system overviews
are best written towards the end of the development of a release because
you know what you've actually built. "
My experience has been the opposite...especially when you like to meet
deadlines and commitments.
2) "No one ever got promoted for having comprehensive documentation
If your job is to create comprehensive documentation, then if you do it
well, you are doing your job well and isn't that what some promotions