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.
Subject:Re: Tech Writing Problems From:"Susan W. Gallagher" <sgallagher -at- STARBASECORP -dot- COM> Date:Tue, 28 Feb 1995 13:05:08 -0800
Problems? Us? Have Problems??? Well... Since you
mention it...
I agree with *all* the problems on Sue Heim's list. In
fact, it sounds like she works down the hall! But just
to add a thought or two...
What about the "it's just English so how hard could
it be" attitude? You know, just because I work in
English and they work in C++, I couldn't possibly
know anything about their work but they know
*everything* about mine (like how to organize a
chapter so that it makes sense).
And then there's a change in the artwork from the
marketing department -- without any input from me
or anyone else on the development team -- one week
before the product is supposed to ship! That leaves
me with a week to completely redo all screen and
book graphics *and* do the final edits and layout!
Have we mentioned the problems that occur when a
single writer is supporting 8 - 10 developers and
six products??? (You want it *when*???)
And how about the inline release of a software
product that results in the manual being obsolete
for 90% of the product life because you don't have
time and they don't have money to change it?
I just can't go on (swoon)...
Sue Gallagher
StarBase Corp, Irvine CA
sgallagher -at- starbasecorp -dot- com
