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: Definition of Tech Writer, was STC is broken From:Ned Bedinger <doc -at- edwordsmith -dot- com> To:Gene Kim-Eng <techwr -at- genek -dot- com> Date:Fri, 02 May 2008 16:53:26 -0700
Gene Kim-Eng wrote:
> No, if you have a driver's license it doesn't automatically mean
> you can just take an Indy car out. Someone with years of
> experience racing Indy cars can't just jump behind the controls
> of a combine harvester or the NASA Crawler, either. But it's
> all still "driving."
>
> The distinction being described here is merely the difference
> between two highly specialized forms of very technical writing.
> No, I wouldn't argue that anyone with experience as a "technical
> writer" can easily make a jump to writing business or finance
> documentation or vice versa, but there are any number of types
> of science, engineering, medical, etc., writing that also require
> highly specialized knowledge and backgrounds to work at their
> most advanced levels as well.
>
> What I see happening in this discussion is that there are a lot
> of people here who seem to believe that technical writers can
> easily jump from any "technical" subject to any other, so any
As contractor, my bread-n-butter can depend on being able to jump and
high. I get a kick out of changing jobs, but absolutely, I've paid the
dues, hopefully all of them if such a condition even exists, to have the
title Technical Writer, and I value it too much to misrepresent it as my
qualification for doing just any technical writing work.
I think maybe this lesson comes with paying the hard dues, which are not
the kind that fold.
> subject that is sufficiently different from what they do, have
> done or can do that they can't make that easy jump must not
> be "technical writing" simply because they can't do it.
There be business writing.
Ned Bedinger
doc -at- edwordsmith -dot- com
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-