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:"Secara, Maggie" <msecara -at- Cayenta -dot- com> To:"'Sierra Godfrey'" <kittenbreath -at- hotbot -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 18 May 2000 13:01:12 -0700
> -----Original Message-----
> From: Sierra Godfrey [mailto:kittenbreath -at- hotbot -dot- com]
> Sent: Thursday, May 18, 2000 12:27 PM
> To: TECHWR-L
> Subject: An Engineer has infected my young mind!
>
> <snip>
>
> How do you all deal with what engineers want and what you
> know should be the correct way to present the info? How do
> you incorporate what the engineer, who knows the most about
> the product, is trying to say, while everyone else knows it's
> hard stuff to learn? Should I rephrase my question?
>
> Thankyou.
> Sierra
>
Let's start with the fact that this engineer is not your boss and doesn't
decide what the manual will look like or how it will be structured. That's
your job. Listen politely, then do what you know is right. If you need
backup, go to your boss who already approves of the job you've been doing.
What I say is, "if you do your job and my job too, what is there left for me
to do?" You don't write his code; he doesn't write your manual.
Cheers!
Maggie Secara
msecara -at- mainsaver -dot- com
"All the world's a stage, Mick, but some of us are dreadfully
under-rehearsed."
