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.
<snip>> she said that it's quite common for manuals,
>release notes, and suchlike things to go out from software companies
>without ever being proofread.
>Is this true in y'all's experience? If it is, does anyone have suggestions
>as to how to keep up quality control in documentation that isn't read by
Cathy, in almsot 10 years, I don't think I've every let anything out the door
without some sort of proofing -- but some of them have been pretty quick
once overs. The reality is that deadlines and budgets don't always allow
for either the time or the fresh eyes that a good edit would require. I try
to get around that by spending any downtime (minutes while I wait for a meeting
and such) looking over random pages of the documents I have on my pate at
the moment. It's not perfect, but in my expereince it's pretty typical.
Technical Communication mta -at- cyberspace -dot- org (h)
& Help System Design mtucker2 -at- e-mail -dot- com (w)