Re: Post on Technical Writing vs. Technical Communication

Subject: Re: Post on Technical Writing vs. Technical Communication
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Fri, 06 Apr 2012 08:39:46 -0400

Maybe not novels, but can any of us truly say that all the tech writing we have done has been totally without fiction? We certainly have been requested to produce fiction.

SME: "The feature isn't in there yet, but just say it is, and I'm sure we'll try to have to code working for Beta test, or at least by the second or third update after FCS. The fHgcalc() function will take two arguments, the time in milliseconds and the area in meters. No, better make that three. The voltage might be different."

In a case like that, whatever we write is bound to be fiction.

In times of great stress I have been known to produce poetry. Fortunately most of it has been lost.

On Fri, 06 Apr 2012 08:04:37 -0400, Cardimon, Craig <ccardimon -at- m-s-g -dot- com> wrote:

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?"

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
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