Re: Post on Technical Writing vs. Technical Communication

[Gene Kim-Eng <techwr -at- genek -dot- com>]

As a name for the field, I don't have a problem with "communications."

I actually don't have that big of an issue with people who want to call
themselves "communicators," although why they'd want to say that on a
resume instead of laying claim all the more specific and recognizable
titles they're qualified to hold is a mystery to me.  It's way better than
some of the goofy things people were calling themselves during the dotcom
boom.

Gene Kim-Eng


On Wed, Apr 4, 2012 at 8:45 AM, Richard L Hamilton <dick -at- rlhamilton -dot- net>wrote:

> I'd prefer not to start a Flame War:-), so Instead I'll ask a practical
> question.
>
> If you were publishing an introductory book on this field, would you use
> Technical Writing or Technical Communication in the title?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives