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: Versatility - how much is a good thing? From:Bob Morrisette <writer1 -at- SABU -dot- EBAY -dot- SUN -dot- COM> Date:Tue, 17 Aug 1999 09:49:00 -0700
Lindsey (LDurway -at- PAV -dot- COM) says:
>A technical writer produces customer-oriented
>documentation that is integral to the product. Period.
>Internal documents are the responsibility of the people who use them.
>When you can't wriggle out of an internal doc job,
>make it inconvenient for them. Ask too many questions.
>Misunderstand their requests.
And act like a total idiot?
Imagine, all these years I thought I was a technical writer and
Lindsay says I'm not.
Writing assembly instructions, test procedures, and ISO policies
and procedures has always been a part of technical writing and
always will be.
Damn, now I have to create a new title for myself and the rest
of the group.
Bob Morrisette
writer1 -at- sabu -dot- ebay -dot- sun -dot- com
