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: "'Steve Janoff (non-Celgene)'" <sjanoff -at- celgene -dot- com>, "'techwr-l -at- lists -dot- techwr-l -dot- com'" <techwr-l -at- lists -dot- techwr-l -dot- com>, 'Dan Goldstein' <DGoldstein -at- riveraintech -dot- com>
Date: Wed, 4 Apr 2012 19:04:34 +0000

We really are information engineers, but getting a title with the word "Engineer" in it would not be easy.

-----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 Steve Janoff (non-Celgene)
Sent: Wednesday, April 04, 2012 3:03 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com; Dan Goldstein
Subject: RE: Post on Technical Writing vs. Technical Communication

Dan Goldstein wrote:

> 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).

You mean he would have *defenestrated* you. :)

Sorry, couldn't resist.

Steve

PS - My favorite title over my career was "Senior Information Engineer" -- had just that little extra edge. Being called an "Engineer" is very cool for a Tech Writer. Wins points among developers.

*********************************************************
THIS ELECTRONIC MAIL MESSAGE AND ANY ATTACHMENT IS CONFIDENTIAL AND MAY CONTAIN LEGALLY PRIVILEGED INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR INDIVIDUALS NAMED ABOVE.
If the reader is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender to notify us of the error and delete the original message. 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


Follow-Ups:

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
RE: Post on Technical Writing vs. Technical Communication: From: Steve Janoff (non-Celgene)

Previous by Author: Technical editing drinking game
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