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: Not Wanted--Technical Writers From:Chris Hamilton <chamilton -at- GR -dot- COM> Date:Tue, 16 Dec 1997 11:06:25 -0600
1. These poets and polisci majors are, in fact, becoming technical
writers by the action of writing technical material. A technical writer
is someone who can write and explain things that are technical. This is
almost the (wince) certification argument in reverse: not experienced or
certified is better. The stance is the opposite, but its limitations are
2. The article seems to be dealing writing that isn't on the technical
side. To do the job with the product I'm working on, you either have to
be "entrenched in the subject matter" or you don't understand it.
I challenge anyone without substantial technical experience to document
our product (a multi-tiered distributed application server) without
going way past deadline or irritating the hell out of the developers
trying to meet _their_ deadlines.
3. The information overload problem described is as much a management
problem as a technical writer problem. Or, in other words, I would've
made it shorter if I had the time.
Chris Hamilton, Senior Technical Writer
Greenbrier & Russel
chamilton -at- gr -dot- com
The opinions listed in this message are mine. No one claimed them after
30 days, so I get to keep them. They do not reflect the views of
Greenbrier & Russel, Inc.