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.
RE: Post on Technical Writing vs. Technical Communication
Subject:RE: Post on Technical Writing vs. Technical Communication From:"Combs, Richard" <richard -dot- combs -at- Polycom -dot- com> To:Bill Swallow <techcommdood -at- gmail -dot- com> Date:Wed, 4 Apr 2012 10:03:50 -0700
Bill Swallow wrote:
> But if you write technical documentation, then yes, you are a
> technical writer. It's the most descriptive term for what you do. If
> you go beyond that to also write a myriad of supporting pieces that
> find their way into marketing, sales, support, research, and social
> spheres, then maybe technical writer is not the most descriptive title
> for you to use. Overworked & Overdistributed Content Junkie might
> work. ;) Or, Technical Communicator.
Cute, but I don't follow the logic.
If you "_write_ technical documentation," you're a technical writer. But if you "_write_ a myriad of" other stuff, you should replace the word _writer_ in your title?
Seems to me it makes more sense to replace _technical_ with a term that encompasses that myriad of _other_ stuff that you _write_. :-)
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-903-6372
------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.