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.
So how does the previously mentioned title of "information developer" grab you?
-----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 Keith Hood
Sent: Wednesday, April 04, 2012 7:12 PM
To: Gene Kim-Eng; Andrew Warren
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Post on Technical Writing vs. Technical Communication
I would prefer to be called a technical writer no matter what exact functions I perform. I think the word âcommunicatorâ is too vague and open to misinterpretation. You could say that the booth babes at a consumer electronics trade show are technical communicators. After all, they are distributing what is supposed to be information about high-tech items. So technically, they are communicating.
I abhor the idea of using the word "engineer" in connection with what we do.The phrase "information engineer" sounds to me like delusions of grandeur. I have too much respect for engineering to apply the title to a job where the most important thing I may do in a day is decide what size to make a screen capture in a PDF.Â
Engineering is working in things that can be quantified and expressed in math. We work with color preferences and hyperlinks. When we finally come up with a formula that provides repeatable valid results for estimating minutes per page to create a help system, then we can call ourselves engineers.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
