RE: Post on Technical Writing vs. Technical Communication

Subject: RE: Post on Technical Writing vs. Technical Communication
From: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>
To: 'Dan Goldstein' <DGoldstein -at- riveraintech -dot- com>, "'techwr-l -at- lists -dot- techwr-l -dot- com'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 4 Apr 2012 13:07:41 +0000

Agreed. What I do is by no means limited to writing.

-----Original Message-----
From: techwr-l-bounces+ccardimon=m-s-g -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+ccardimon=m-s-g -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Dan Goldstein
Sent: Wednesday, April 04, 2012 9:04 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Post on Technical Writing vs. Technical Communication

And by the way, when I worked for Neil, if I had tried to limit my job to *only* writing, he'd have shoved me out the window (if we'd had a window, which we didn't). Graphics, Web design, project management... it was all in there. But we call it tech writing.

Now I'm a Quality Assurance Manager for an FDA- and MDD-regulated medical device manufacturer, and my responsibilities are wonderfully diverse. But if you put it in a job description and slapped "Senior Technical Writer" at the top, no good tech writer would be surprised.


-----Original Message-----
From: Cardimon, Craig
Sent: Wednesday, April 04, 2012 8:49 AM
To: Dan Goldstein; 'techwr-l -at- lists -dot- techwr-l -dot- com'
Subject: RE: Post on Technical Writing vs. Technical Communication

I love that definition since I definitely write documentation for a living.


-----Original Message-----
From: Dan Goldstein
Sent: Wednesday, April 04, 2012 8:46 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Post on Technical Writing vs. Technical Communication

Then there's always Neil Churgin's definition: "A technical communicator communicates to others that they are not a technical writer and watch out if you call me one. A technical writer works for a living."


-----Original Message-----
From: Cardimon, Craig
Sent: Wednesday, April 04, 2012 8:22 AM
To: 'TechWhirl (techwr-l -at- lists -dot- techwr-l -dot- com)'
Cc: Cardimon, Craig
Subject: Post on Technical Writing vs. Technical Communication

I came across a good post today on the difference between Technical Writing and Technical Communication.

http://pidgeperry.wordpress.com/2012/04/03/technical-communications/




This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 ccardimon -at- m-s-g -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
Information contained in this e-mail transmission is privileged and confidential. If you are not the intended recipient of this email, do not read, distribute or reproduce this transmission (including any attachments). If you have received this e-mail in error, please immediately notify the sender by telephone or email reply.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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: Dan Goldstein
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
RE: Post on Technical Writing vs. Technical Communication: From: Dan Goldstein

Previous by Author: RE: Post on Technical Writing vs. Technical Communication
Next by Author: RE: Post on Technical Writing vs. Technical Communication
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