RE: TC vs TW

Subject: RE: TC vs TW
From: David Hailey <david -dot- hailey -at- usu -dot- edu>
To: Gene Kim-Eng <techwr -at- genek -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 8 May 2008 14:35:50 -0600

My model for someone with decent long-term professional prospects (either as an in-house employee or a successful self-employed vendor/consultant) is someone with hands-on experience as an engineer, scientist, project manager, programmer, service technician, etc., plus what you're teaching under the "communications" program. Anyone else is seriously at-risk for being unemployable except as an hourly worker

I think you are absolutely correct. But . . .

. . .and the non-writing "communicator" jobs that I predicted will degrade to hourly support jobs will follow to wherever the "nontechnical" technical writer jobs end up (everybody today worries about India, but I think ten years from now India will be looking for someplace to offshore as well).

The "technical communicators" that I suggest don't write include technical animators (who will probably end up overseas), and communications directors (or people who are qualified to be communications directors, creative directors, project managers, publication coordinators, managing editors, etc.), who will probably not go overseas. These are the positions well educated technical communicators with a habit of life-long learning tend to fill. The positions require some, but not much of the technical-professional background Kim-Eng requires, but typically, they require significant knowledge of current publication processes, tools, and laws. These are the positions that are less likely to get outsourced.

As to titles? I agree with those who say titles are unimportant . . . but, I suggest that what you do is important.

David E. Hailey, Jr., Ph.D.
Associate Professor -- Professional and Technical Writing
Utah State University
dhailey -at- english -dot- usu -dot- edu


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!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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 for more resources and info.


TC vs TW: From: Technical Writer
Re: TC vs TW: From: Gene Kim-Eng
RE: TC vs TW: From: Technical Writer
RE: TC vs TW: From: David Hailey
RE: TC vs TW: From: Leonard C. Porrello
Re: TC vs TW: From: Gene Kim-Eng
RE: TC vs TW: From: David Hailey
Re: TC vs TW: From: Gene Kim-Eng
RE: TC vs TW: From: David Hailey
Re: TC vs TW: From: Gene Kim-Eng

Previous by Author: RE: TC vs TW
Next by Author: RE: successful offshoring of TC/TW (was: TC vs TW)
Previous by Thread: Re: TC vs TW
Next by Thread: Re: TC vs TW

What this post helpful? Share it with friends and colleagues:

Sponsored Ads