RE: Top ten myths of technical communication

Subject: RE: Top ten myths of technical communication
From: "Halter, Meg" <HalterMC -at- navair -dot- navy -dot- mil>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 18 Oct 2000 12:57:08 -0700

Heh, maybe this means I'm going the wrong way again. Engineering and code
development to tech writing. Maybe that explains the questions I've gotten
that start helpfully with "Now that you're doing secretarial work..."
(That's the sound of my teeth gnashing.)

-- Meg

> -----Original Message-----
> From: BMcClain -at- centura -dot- com [SMTP:BMcClain -at- centura -dot- com]
> Sent: Wednesday, October 18, 2000 10:23 AM
> To: TECHWR-L
> Subject: RE: Top ten myths of technical communication
>
> One odd misconception of technical writing that senior P/As have voiced to
> me in various jobs: The natural career progression of technical writers
> is
> for them to eventually become programmers. Apparently the rationale is
> that
> with increasing experience in software development, TWs finally slide into
> developing specs with SMEs, then discovering high-level user requirements,
> and finally they wind up writing the code instead of "merely" explaining
> it.
> However, nobody who's suggested this myth to me could come up with more
> than
> anecdotal evidence of this progressive career change.
>
> Bill McClain
> ("Writers are always selling somebody out." - Joan Didion)
>
>




Previous by Author: Re: Simultaneous Author Access to files
Next by Author: Questions about help authoring
Previous by Thread: RE: Top ten myths of technical communication
Next by Thread: RE: Top ten myths of technical communication


What this post helpful? Share it with friends and colleagues:


Sponsored Ads