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: 'Keith Hood' <klhra -at- yahoo -dot- com>, 'Gene Kim-Eng' <techwr -at- genek -dot- com>, 'Andrew Warren' <awarren -at- synaptics -dot- com>
Date: Fri, 6 Apr 2012 12:04:37 +0000

The only problem with telling people you are a professional writer, from what I can see, is that they immediately assume you write novels, not procedures or instructions or user guides.

Me: "Hi, I'm a professional writer."
Them: "Wow! That's great! What books have you written?"

Or

Me: "Hi, I'm a technical writer."
Them: "Oh. What's that?"

From: Keith Hood [mailto:klhra -at- yahoo -dot- com]
Sent: Thursday, April 05, 2012 8:17 PM
To: Cardimon, Craig; 'Gene Kim-Eng'; 'Andrew Warren'
Cc: 'techwr-l -at- lists -dot- techwr-l -dot- com'
Subject: Re: Post on Technical Writing vs. Technical Communication

It doesn't. To me the phrase 'developing information' is too nebulous. What the heck is 'developing'? It could be sorting and filtering a spreadsheet. A so-called i-reporter can say he's developing information when he asks questions and transmits blurry pictures at the riot. You can develop camera film - that doesn't make you a photographer.

On the other hand, the word 'writing' is unmistakable. It implies producing a tangible, usable product.

I write about highly technical subjects, using a style of writing tailored for the purpose of creating items that impart technical information in a clear manner. That's what I do whether I'm producing a PDF, a PowerPoint slide show, or a set of software functional requirements. I like being called a writer. Among other things, it implies creativity. And I think there is an element of creativity in this work.

To some extent, it's a form of bragging. I can truthfully tell people I am a professional writer, that I have made my living from writing for more than 20 years. If I tell someone I've been a developer for more than 20 years he'll give me the stunned mullet look because he won't have any idea what I mean.


________________________________
From: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com<mailto:ccardimon -at- M-S-G -dot- com>>
To: 'Keith Hood' <klhra -at- yahoo -dot- com<mailto:klhra -at- yahoo -dot- com>>; 'Gene Kim-Eng' <techwr -at- genek -dot- com<mailto:techwr -at- genek -dot- com>>; 'Andrew Warren' <awarren -at- synaptics -dot- com<mailto:awarren -at- synaptics -dot- com>>
Cc: "'techwr-l -at- lists -dot- techwr-l -dot- com'" <techwr-l -at- lists -dot- techwr-l -dot- com<mailto:techwr-l -at- lists -dot- techwr-l -dot- com>>
Sent: Thursday, April 5, 2012 8:50 AM
Subject: RE: Post on Technical Writing vs. Technical Communication

So how does the previously mentioned title of "information developer" grab you?

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)
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
RE: Post on Technical Writing vs. Technical Communication: From: Steve Janoff (non-Celgene)
Re: Post on Technical Writing vs. Technical Communication: From: Peter Neilson
Re: Post on Technical Writing vs. Technical Communication: From: Gene Kim-Eng
Re: Post on Technical Writing vs. Technical Communication: From: Peter Neilson
RE: Post on Technical Writing vs. Technical Communication: From: Andrew Warren
Re: Post on Technical Writing vs. Technical Communication: From: Gene Kim-Eng
Re: Post on Technical Writing vs. Technical Communication: From: Keith Hood
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
Re: Post on Technical Writing vs. Technical Communication: From: Keith Hood

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