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: An Engineer has infected my young mind! From:Christi <christi -at- sageinst -dot- COM> To:Sybille Sterk <sybille -at- wowfabgroovy -dot- net>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 18 May 2000 15:35:16 -0700
on 5/18/00 3:26 PM, Sybille Sterk wrote:
<snip>
> The engineer has no business telling you what to put into the manual. You
> are not telling him what to put into the program, are you?
Whoah. I'm usually all for "we are the tech writer and we know best". But I
think this takes it a bit far. I don't think I've ever written a guide
without some input from the engineer (developer, programmer, whatever title
they like). And yes, actually, I do tell them what to put and not put in the
program. If, that is, I think my input would benefit the user and it's
something the developer hasn't thought of or seen or considered.
I think there is more (or should be more) conversation between the TW and
Eng. and I suspect that both sides will have (at least some) valuable input
to both processes.
Christi Carew
Technical Writer
Sage Instruments
Freedom, CA, USA
www.sageinst.com
The early bird gets the worm, but the second mouse gets the cheese.
- Stephen Wright
