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.
Subject:Re: technical Writing Skills From:Mean Green Dancing Machine <aahz -at- NETCOM -dot- COM> Date:Thu, 9 Feb 1995 13:29:11 GMT
In article <3hboh1$fc1 -at- lester -dot- appstate -dot- edu>,
Matt Harmon <mh1704 -at- acs -dot- appstate -dot- edu> wrote:
>On Wed, 8 Feb 1995 15:40:46 GMT, Mean Green Dancing Machine (aahz -at- netcom -dot- com)
>> Normally, I'd say writing ability is more important. However, it can be
>> critically important to have a tech writer who really understands the
>> problem domain. In my first and only job as a tech writer, my ability
>> to program in C turned out to be crucial in writing the manual, in large
>> part because I was able to get the programmer to change the product
>> design in certain ways that made it easier to document.
> Meaning no disrespect but, shouldn't a good technical writer be able to
>get around any aspects that make a product difficult to document? This is
>what's always been expected of me (English major, Computer Information Systems
>minor and documentation specialist for a local computer/network project).
> No-one ever said this job was easy--that's why tech writers are
>compensated as they are.
I guess I should have been more explicit -- generally something that is
easier to document is easier to use.
--- Aahz (@netcom.com)
Hugs and backrubs -- I break Rule 6
Androgynous kinky vanilla queer het
"First one back from the bathroom gets to be the bottom."