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.
From:Herman Holtz <holtz -at- CLARK -dot- NET> Date:Wed, 1 Mar 1995 10:28:16 -0500
Among the many observations about the typical problems of tech writers
have been many about difficulties in getting information. In my own time
in tech writing, inasmuch as the bulk of the work in thsoe days was in
writing manuals about hardware, we were often compelled to rely on our
own analyses of engineering schematic drawings of the equipment. What are
some of the typical sources of data today--for writing a software manual,
for example? What would be the worst case--e.g., depending on your
ability to read the code? Do you get bug reports? Beta test results? Etc.
* * *
Herman Holtz [holtz -at- clark -dot- net]: Marketing Consultant/Proposal Specialist,
Writing & Ghost Writing Services, 35 years experience. Author of 60+
professional/business books, including best-selling How to Succeed as an
Independent Consultant (Wiley). PO Box 1731, Wheaton, MD 20915. Tel:
301-649-2499. Fax: 301-649-5745.
