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: Flawed software From:Tom Lange <Tom_Lange -at- CCMAIL -dot- BMC -dot- COM> Date:Thu, 1 Feb 1996 09:41:19 CST
I have yet to see perfect documentation for an unflawed software
product. Actually, I have yet to see an unflawed software product.
However, (now that I have the humor out of the way) it is possible to
write documentation that makes a badly flawed product look less
flawed. It is even possible (not easy, but possible) to use
documentation to make some, most, or all of the flaws or bugs look
like real features by writing about what the flaw does, not about what
it does not do.
Of course, I have not figured out how to write anything positive about
some of them. A general protection fault brings a computer to a
screeching halt. Coming to a screeching halt may be a benefit if I
were writing about tires or brakes on a car; however, in a
Just one Texan's opinion.
tom_lange -at- ccmail -dot- bmc -dot- com