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: Do you do QA? From:"Wing, Michael J" <mjwing -at- INGR -dot- COM> Date:Tue, 30 Jul 1996 15:45:39 -0500
>My coworker and I were recently informed that we were expected to
>perform QA
>functions in addition to our writing responsibilities, and that QA
>engineers
>would also be responsible for writing end-user documentation. In our
>combined
>25+ years of experience, we have never been asked to do such a thing.
>We do not
>have the training to do real QA testing.
>Certainly we do usability testing as part of our job functions. We
>evaluate the
>design of a product to ensure that it doesn't hinder the user rather
>than help
>him do his job. But it seems odd to label us "QA test
>engineers/technical
>writers" when we also design and create a product that needs to be QA
>tested.
>I'd like the opinions of other writers. Am I being unreasonable in
>resisting
>this arrangement?
>Thanks!
>Karen
I've done some certification (actually volunteered to get one product
out) along with development of automation test code and database
extraction/symbolization rulesets. I have been recruited during some
software testing cycles because having documented the entire package, I
am one of the few people who see the product as a collection of related
pieces rather than stand-alone components (feeding and fed by black
boxes). The testing also force-fed me to follow my own instructions
(who wrote these $#&* instructions anyway).
The downside was the cert plans, filing and tracking TRs, reloading
software, verifying installation, and so forth.
It's not just QA hat that has found it's way on my head, I've been
called in to teach customer classes (one through a Chinese interpreter -
you think with the last name Wing (with is of Danish extraction), I
would speak Chinese), do field training and installation, and handle
sales calls. On one project in my former company, I did the circuit
board layout, wirewrap, soldering, testing, ATE testing code, on-site
training, test plans, and the manual.
Hey, it's the 90s. With downsizing the trend, it's better to build your
skills horizontally (across disciplines) than vertically.
Mike Wing
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>_/
>_/ Michael Wing
>_/ Principal Technical Writer
>_/ Jupiter Customization and Educational Services
>_/ Intergraph Corporation
>_/ Huntsville, Alabama
>_/ (205) 730-7250
>_/ mjwing -at- ingr -dot- com
>_/
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-