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.
RE: Technical writer survey: What should we really call ourselves?
Subject:RE: Technical writer survey: What should we really call ourselves? From:"Adrianne Mora" <AdrianneM -at- envipco -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 12 Aug 2009 14:16:47 -0400
I thought of it as expressing that I am not solely a writer but that I
also have experience in training and public speaking. Since I respect
Gene's wisdom and experience, I'll have to rethink that.
-----Original Message-----
From: techwr-l-bounces+adriannem=envipco -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+adriannem=envipco -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Gene Kim-Eng
Sent: Wednesday, August 12, 2009 1:44 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Technical writer survey: What should we really call
ourselves?
You can probably guess what my initial impression on seeing
"communicator" at the top of a resume sent in response to an opening
that I post as "writer" would be.
The thought behind my impression is generally that the individual who
feels the need to self-present as a "communicator" when I've advertised
for a writer is going to turn out to be someone who either lacks the
necessary skills for my writer position and is trying to "puff up" the
resume, will tend to devote more time and effort to trying to push
changes in style and delivery methodology than developing actual
technical content, suffers from an inferiority complex over being
thought of as a writer, or just can't read a job listing. None of these
are particularly desirable in a candidate.
Of course, if you're applying for a position that is actually listed as
"communicator," you need to do what you need to do if you want the job.
But as a writer, I would probably have all of the above concerns about
the working environment.
Gene Kim-Eng
----- Original Message -----
From: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>
> Some would say "communicator" is a $20 word and "writer" is a $10
> word.
> Many people are only paying for the $10 word. You can call yourself a
> communicator if you want, but you're being paid as a writer (provided
> you actually write stuff). Like it or not.
Please take care of the environment. Print only if necessary..
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-