RE: Post on Technical Writing vs. Technical Communication

Subject: RE: Post on Technical Writing vs. Technical Communication
From: "Steve Janoff (non-Celgene)" <sjanoff -at- celgene -dot- com>
To: "'techwr-l -at- lists -dot- techwr-l -dot- com'" <techwr-l -at- lists -dot- techwr-l -dot- com>, "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>
Date: Wed, 4 Apr 2012 13:16:47 -0700

Titles are usually mandated by the company. I thought this was a great policy on their part. (It was a large company, and I believe they'd inherited the titles from the even larger company they'd spun off from, NCR.)

I would think the STC would have to lobby for a title change at that level.

I wonder how they'd take to changing their name to Society for Information Engineering (SIE).

It was a great title (Senior Information Engineer), and I really miss it. But unless you're working for a startup where they might let you get away with choosing your own title, it's pretty much going to be luck of the draw.

Steve

PS - By the way, I like Information Engineer better than Information Developer, which I'd also had at an earlier job. The latter just doesn't have the same heft as the former.

Craig Cardimon wrote:

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


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

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