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.
> My response to you is this: Keep your structure until I fix the other
> problems. Then we can talk.
On this one, I agree with Dan Emory.
If you could track it back in the history of the doc set's development, lack
of structure was probably the biggest contributor to the "other problems."
Most documentation flaws I have encountered were directly due to poor, or
more commonly, no specifications, market requirements, and software
development process.
Occasionally I've encountered cases where the writer did a poor job, but
most often, when I inquired and found out the conditions under which the
work was done, I was impressed it had turned out so well.
