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: Certification From:Tracy Boyington <trlyboyi -at- GENESIS -dot- ODVTE -dot- STATE -dot- OK -dot- US> Date:Thu, 4 Jan 1996 08:11:30 +0000
Rick Lippincott wrote:
> There is another huge problem that
> we've overlooked: hardware vs. software. The expertise required for one type
> tech communication is far different from the knowledge required for the
> A hardware tech writer might need to know things such as tensile strengths,
> metallurgy, non-destructive inspection, high-voltage or high-temperature
> effects, corrosion control, torque values.... whew, the list goes on and on.
> It's quite likely that the hardware tech writer does -not- need any
> skills, nor the slightest clue how to read code.
And what about those of us who write about neither hardware nor
software? Or am I the only one? If we *do* get into certification,
which I'm still not convinced is a great idea, it would have to be
certification of basic communication skills, not whether you can read
code or perform non-destructive inspection. Unless you wanted to get
into specialty areas, I suppose.
Technical Communication Specialist
Oklahoma Department of Vocational & Technical Education
I never express opinions, but if one slips out, it belongs
to me and not ODVTE.
"I think I did pretty well, considering I started out
with nothing but a bunch of blank paper."
-- Steve Martin