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: More title questions From:"Raj Machhan" <raj -dot- machhan -at- gmail -dot- com> To:"Janice Gelb" <Janice -dot- Gelb -at- sun -dot- com> Date:Tue, 27 Nov 2007 03:45:54 +0530
The idea behind discussing the designations used in newspapers and
magazines is to examine the possibility of whether these can be
adopted in a Tech Comm set up. Janice seems to have missed a key
point: It is the writer who graduates to the position of an editor and
not vice-versa. So there is no confusion of roles here. For example,
in a newspaper, the news editor ( a position somewhat similar to
Technical editor in Tech Comm) is expected to have the ability to
write well. But a Staff Correspondent (comparable to a Technical
writer for our purpose) is not required to posses any editing skills.
This is just one of the possibilities for standardizing the
designations in Technical Communications. Janice talks about another
possibility using the hyphenated or slashed title. I suggest we could
go through the merits of each option to arrive at the best fit
On 11/27/07, Janice Gelb <Janice -dot- Gelb -at- sun -dot- com> wrote:
> Raj Machhan wrote:
> > Editor as a designation has its moorings in the print media. It is widely
> > used to describe the pecking order in newspaper and magazines. So we have
> > sub-editors, deputy editors, assistant editors, associate editors and so
> > with the editor-in-chief as the top boss. However, the job profile of
> > editorial positions (excluding the overworked sub-editors, who lie at the
> > bottom of the pile) also involves a fair amount of writing.
> > I do not see any reason why we cannot apply the same structure, in a
> > way, to positions in a Technical Communications set up. So instead of
> > having designations such as "technical writer editor", or "technical
> > and editor" we could simply put it as "technical editor", "sr technical
> > editor" and so on. The designations need to be standardized to avoid
> > confusion.
> My job is that of a technical editor and although
> I have written some of our internal tools documentation
> manuals, that is not my primary job function. I imagine
> the writers on here will object as much as I do to a
> job title that implies that their primary function is
> to edit! Editing and writing are different jobs with
> different responsibilities and although often people
> must do both in their working environment, that doesn't
> mean that the titles can or should be combined.
> I don't think that writers who occasionally do peer
> editing to catch overlooked obvious errors because their
> company does not employ editors should append "editor"
> to their titles. You only need to invent a hyphenated
> or slashed title if your editing responsibilities are
> equal to or on the same professional standing as your
> writing responsibilities.
> -- Janice
> Janice Gelb | The only connection Sun has with
> janice -dot- gelb -at- sun -dot- com | this message is the return address
> 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.
> 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 raj -dot- machhan -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
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-