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: Novelists & other good writing From:Vignes Gerard M <gmv0570 -at- UCS -dot- USL -dot- EDU> Date:Tue, 13 Apr 1993 05:40:09 GMT
In article <29111 -dot- csvmja -at- admin -dot- ac -dot- edu> "Maureen J. Akins" <csvmja -at- admin -dot- ac -dot- edu>
>As a Computer Support Specialist (a troubleshooter, an instructor, a
>technical writer, and a programmer), I've found that my best experience has
>come from introducing beginners to computers. Once you've seen how
>instructions can be misinterpreted, or how incomplete instructions can be a
>source of panic, you can begin to understand why it is an art to write well.
A corollary to your observation might be the statement:
"to be a good technical writer, one must first become
an accomplished reader of technical literature."
I suspect that you must have spent many hundreds of hours
teaching yourself from tutorials and manuals in order to
be able to help others, and that experience has given you
the perspective to become a truly competent technical writer.