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: Why We Need Good Software Manuals From:Kent Newton <KentN -at- METRIX-INC -dot- COM> Date:Wed, 24 Jan 1996 18:44:00 PST
Just so everyone knows, I wrote the quoted material that made the reader
see red. the way the message was snipped may have led some readers to
assume Jane wrote it. She was merely quoting me. Wanted to set the
record straight.
Kent Newton
Senior Technical Writer
Metrix, Inc.
kentn -at- metrix-inc -dot- com
----------
From: TECHWR-L[SMTP:TECHWR-L -at- listserv -dot- okstate -dot- edu]
Sent: Wednesday, January 24, 1996 10:44 AM
To: Multiple recipients of list TECHWR-L
Subject: Re: Why We Need Good Software Manuals
see red, below (I did.)
----------
From: Jane Bergen[SMTP:janeb -at- answersoft -dot- com]
Sent: Wednesday, January 24, 1996 1:26 AM
To: Multiple recipients of list TECHWR-L
Subject: Re: Why We Need Good Software Manuals
> It's a shame when a technical writer won't even read a technical
> manual.
> Besides learning to use the product, it is good research to see how
> other writers solve thorny problems, what new tricks are being used,
> and how complex material can be organized. I think it would be a
> natural reaction for every tech writer to read (or at least skim)
> any documentation they can get theirs hands on -- especially for the
> software they uses.
