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.
> Gene wrote: "My first thought when I hear of technical writers trying
to get their titles changed to "technical communicator," "information
developer," etc., is that it must be a terrible thing to be working in a
place where being called a writer causes one to develop such an
inferiority complex."
It's an interesting thought, but I don't think it comes down to ego and
insecurity. Someone with acute or chronic insecurity would not last long
as a technical writer, and none of the people who have contributed to
this thread seem to lack temerity.
I think it is a matter of economics: "What title will best convey to the
market the full scope of my skills?" I personally tend to go with the
hypothesis that "technical writer" is the safest bet, but at the same
time, I wouldn't try to slam those who prefer "Technical Communicator"
unless I had empirical evidence.
Is there one person reading this thread who wouldn't accept a change in
title if doing so meant more pay?
Leonard C. Porrello
-----Original Message-----
From: techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of Sam Beard
Sent: Wednesday, May 07, 2008 7:29 AM
To: Gene Kim-Eng; Bonnie Granat; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Definition of Tech Writer, was STC is broken
Gene,
I LIKE your first thought!
Samuel I. Beard, Jr.
Technical Writer
OI Analytical
979 690-1711 Ext. 222
sbeard -at- oico -dot- com
-----Original Message-----
From: techwr-l-bounces+sbeard=oico -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+sbeard=oico -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf
Of Gene Kim-Eng
Sent: Tuesday, May 06, 2008 6:00 PM
To: Bonnie Granat; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Definition of Tech Writer, was STC is broken
My first thought when I hear of technical
writers trying to get their titles changed to
"technical communicator," "information
developer," etc., is that it must be a terrible
thing to be working in a place where being
called a writer causes one to develop such
an inferiority complex.
Ok, that's actually my second thought. The
first time I ever heard the term "technical
communicator," my first thought was "it's
that badge that people on Star Trek tap
whenever they want to call the guy in
Engineering, right?"
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
Leonard -dot- Porrello -at- soleratec -dot- com -dot-
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-
