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.
I am guessing it would be best to contact me off list, rather
than start a firestorm of differing opinions.
To which Russell Griechen responds:
I would think you would want all the different opinions that would be
spawned by posting their answers to the list.
At tech writer level I would assume a dispassionate discourse would be a
normal result.
I, too, was surprised that Ms. Nelson felt there would be a "firestorm of
differing opinions" about what a Technical Writer does. I would expect
comments on the topic to be additive rather than exclusive. After listening
to TWs from various organizations and geographic locations describe what
they do, I am convinced that we do different things depending on the needs
and practices we find.
I was equally taken aback by Mr. Griechen's comment that "dispassionate
discourse would be a normal result." Russ, you're new to the list, right?
Truly, it is a shame that we can argue so passionately over such trivia as
whether or not it is demeaning to a TW to edit someone else's copy. And it
is a shame that we drive away good reasoned discourse out of fear of
starting a flame war.
To me, this is a more important topic that what the job description of a TW
is or should contain.
Tom Murrell
Sometimes I write, and sometimes I edit.
But I'm always a writer.