RE: So now we are content engineers?

Subject: RE: So now we are content engineers?
From: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>
To: 'Dan Goldstein' <DGoldstein -at- cytomedix -dot- com>, "'techwr-l -at- lists -dot- techwr-l -dot- com >> TECHWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 6 Nov 2013 18:41:21 +0000

I enjoy my title of "Technical Writer." I worked hard for it.

-----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, November 06, 2013 1:36 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com >> TECHWR-L
Subject: RE: So now we are content engineers?

Very amusing. Let me know when a respected engineering school starts granting degrees in Content Engineering.

Until then, Mark Baker is just a plain ol' technical writer like the rest of us. If it's any comfort, I happen to think it's an honorable job title.


-----Original Message-----
From: Erika Yanovich
Sent: Wednesday, November 06, 2013 1:21 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com >> TECHWR-L
Subject: So now we are content engineers?

http://everypageispageone.com/2013/11/04/i-am-a-content-engineer/



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

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

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.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

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

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:
Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: rebecca officer
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Kathleen MacDowell
So now we are content engineers?: From: Erika Yanovich
RE: So now we are content engineers?: From: Dan Goldstein

Previous by Author: RE: So now we are content engineers?
Next by Author: RE: Footnotes - acceptable in technical documentation?
Previous by Thread: Re: So now we are content engineers?
Next by Thread: Re: So now we are content engineers?


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

Sponsored Ads


Sponsored Ads