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: Top ten myths of technical communication From:Sanjay Srikonda <SSrikonda -at- invlink -dot- com> To:"'BMcClain -at- centura -dot- com'" <BMcClain -at- centura -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 18 Oct 2000 13:29:38 -0400
What about us TWs who went the opposite route, from being P/As to the TW
field? Do we count as the natural regression of the orderly state of
affairs? Oh, my, does that mean I'm a throwback?
-----Original Message-----
From: BMcClain -at- centura -dot- com [mailto:BMcClain -at- centura -dot- com]
Sent: Wednesday, October 18, 2000 1:23 PM
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)
<snip>
