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: Not reading manuals like a novel From:SuePStewrt -at- AOL -dot- COM Date:Wed, 15 Mar 1995 03:35:10 -0500
>> But for "training guides" (assuming that you
mean what I would call tutorials )<<
No, I meant TRAINING. I don't think I typed "tutorial." :) Again, *not all
techwriting has to do with computers.* ;-)
Many training guides are designed in sequential lessons which pretty much
must be done front to back, because if you haven't learned task 4 you can't
do task 5, or if you haven't studied the information in chapter 6, chapter 7
will lose you in the first paragraph.
I think I'll stop straining at this particular gnat. But to state "tenets"
which apply to only one kind of technical writing is to ignore the real
world, where tech writers deal with far more than bits and bytes and scsi
connectors.
