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:Kat Kuvinka <katkuvinka -at- hotmail -dot- com> To:<klhra -at- yahoo -dot- com>, <techwr -at- genek -dot- com>, <awarren -at- synaptics -dot- com> Date:Wed, 4 Apr 2012 23:45:41 -0400
>
> 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.
Yeah, that's really just math, not engineering.
>
> Engineering is working in things that can be quantified and expressed in math.
Oh, errrr...
>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.
>
I dunno...color and HTML sounds like more math to me. My feeling is that if a programmer or tester (who may or may not have a degree) can be an "engineer" so can I. I do program on occasion, I'm in the code, I write and execute test plans. Besides, I plan, carry out and manage entire efforts, which is a valid definition of engineering.
Sorta semi-related, I knew a writer in a large company who reached the salary ceiling for her role, and in order to get a raise in that particular organization, she had to be given the title "Software Engineer." So much for descriptive titles.
casey "kat" jones
(no, I don't really think I am an engineer, but neither are programmers/testers...)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
