RE: Post on Technical Writing vs. Technical Communication

Subject: RE: Post on Technical Writing vs. Technical Communication
From: "Dan Goldstein" <DGoldstein -at- riveraintech -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 4 Apr 2012 12:22:15 -0400

Since when are instructional design, e-learning, courseware preparation,
and API documentation *not* part of technical writing? They were the
last time I checked.

I agree that web copy and business communication are often considered
separate from technical writing, though of course many technical writers
do that work as well.


-----Original Message-----
From: Gurpreet Singh
Sent: Wednesday, April 04, 2012 12:08 PM
To: techwrl
Subject: Re: Post on Technical Writing vs. Technical Communication

I'm pursuing a graduate certificate in 'Technical Communication' from
Seneca College, Toronto.

You are absolutely correct that most recruiter and employers are
familiar with the term "Tech Writing" and not "Technical Communication"
and even then the courses in college and universities are about
Technical Communication.

As far as I know, Technical Writing is a subset of Technical
Communication.
Technical Communication is a mother ship for Instructional Designing,
e-learning, courseware preparation, Technical Writing, API
Documentation, web-copy writing and even business communication.

I use the term technical communicator only when I am talking to another
technical writer. My resume and LinkedIn profile still says technical
writer. I'm proud to be one!




This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. 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


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: Gene Kim-Eng
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
Re: Post on Technical Writing vs. Technical Communication: From: Richard L Hamilton
Re: Post on Technical Writing vs. Technical Communication: From: Milan Davidović
Re: Post on Technical Writing vs. Technical Communication: From: Gurpreet Singh

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