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.
I agree with Wendy Warren. Most manuals are
references to be *used* not *read.* That was an
underlying point to my post about the software-type
who does use manuals. He made the point of saying
that he didn't really read any manual, but he
wanted to be able to find info. that he needed by
using the usual clues (index, tabs, toc). When
he found it, he wanted it to be clear and understandable.
One manual that he liked was VAX VMS. Yes, as Steve
noted, it is multi-volume, but it was written to be
a reference, not a "user guide" that might be more
thoroughly read.
My Oxford English Dictionary is huge, but that
doesn't keep me from finding the information that I
want from it!
Hmm... What can I learn from this? It goes back
to our usual theme:
* Establish the PURPOSE of the doc
* Analyze the AUDIENCE of the doc
Maybe it's time to post that song again (I forgot
the name of the author)...
