TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
From: Kat Kuvinka [mailto:katkuvinka -at- hotmail -dot- com]
Sent: Friday, April 06, 2012 9:15 AM
To: Cardimon, Craig; klhra -at- yahoo -dot- com; techwr -at- genek -dot- com; awarren -at- synaptics -dot- com
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Post on Technical Writing vs. Technical Communication
Many people have and still do think that as a technical writer I "write computer programs."
My parents are pretty sure I "do computer stuff."
> 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?"
>
>
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.
