Re: Post on Technical Writing vs. Technical Communication

Subject: Re: Post on Technical Writing vs. Technical Communication
From: Bill Swallow <techcommdood -at- gmail -dot- com>
To: "Combs, Richard" <richard -dot- combs -at- polycom -dot- com>
Date: Wed, 4 Apr 2012 13:06:50 -0400

I know I pigeon-holed myself there with "write" but it could lend
itself to other activities such as graphics work, design work, review
work, UX stuff, UA stuff, video work... You know, all that stuff that
now goes into getting a product out the door.

On Wed, Apr 4, 2012 at 1:03 PM, Combs, Richard
<richard -dot- combs -at- polycom -dot- com> wrote:
> Bill Swallow wrote:
>
>> But if you write technical documentation, then yes, you are a
>> technical writer. It's the most descriptive term for what you do. If
>> you go beyond that to also write a myriad of supporting pieces that
>> find their way into marketing, sales, support, research, and social
>> spheres, then maybe technical writer is not the most descriptive title
>> for you to use. Overworked & Overdistributed Content Junkie might
>> work. ;) Or, Technical Communicator.
>
> Cute, but I don't follow the logic.
>
> If you "_write_ technical documentation," you're a technical writer. But if you "_write_ a myriad of" other stuff, you should replace the word _writer_ in your title?
>
> Seems to me it makes more sense to replace _technical_ with a term that encompasses that myriad of _other_ stuff that you _write_. :-)
>
> Richard G. Combs
> Senior Technical Writer
> Polycom, Inc.
> richardDOTcombs AT polycomDOTcom
> 303-223-5111
> ------
> rgcombs AT gmailDOTcom
> 303-903-6372
> ------
>
>
>
>
>
>



--
Bill Swallow
Content Solutions Manager
GlobalScript, a division of LinguaLinx
http://globalscript.com
http://lingualinx.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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


References:
Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
Re: Post on Technical Writing vs. Technical Communication: From: Bill Swallow
RE: Post on Technical Writing vs. Technical Communication: From: Combs, Richard

Previous by Author: Re: Post on Technical Writing vs. Technical Communication
Next by Author: Re: Technical editing drinking game
Previous by Thread: RE: Post on Technical Writing vs. Technical Communication
Next by Thread: RE: Post on Technical Writing vs. Technical Communication


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

Sponsored Ads


Sponsored Ads