RE: Top ten myths of technical communication

Subject: RE: Top ten myths of technical communication
From: BMcClain -at- centura -dot- com
To: basilisk -at- acm -dot- org
Date: Wed, 18 Oct 2000 14:48:26 -0400

Who ever said reasoning figured into this? :o)

I can say, however, that in all three cases the developers/analysts were
unfamiliar with technical writing and I and my co-workers were usually,
maybe all three times, the first TWs they'd known.

-----Original Message-----
From: Jennifer Freeman [mailto:basilisk -at- acm -dot- org]
Sent: Wednesday, October 18, 2000 2:32 PM
To: TECHWR-L
Subject: RE: Top ten myths of technical communication


Software Engineering methodology usually says that things go in this order:
1. Discovering user requirements
2. Developing specs
3. Writing code
4. (etc.)
so I find it interesting that experienced people would think that technical
writers would come in at the second stage, move to the first, _then_ switch
to the third. Have you (or anyone else who has encountered this phenomena)
ever asked them to explain their reasoning?




Previous by Author: RE: the OTHER test
Next by Author: RE: the OTHER test
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