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:Frequent doc revisions From:geoff-h -at- MTL -dot- FERIC -dot- CA Date:Mon, 7 Oct 1996 08:51:32 -0500
There's another interesting point that I just twigged to
about the "put docs on the web so they're always up to
date" philosophy.
Remember the old GIGO (garbage in, garbage out) rule? The
"garbage in" in this case is the notion that you've got to
keep constantly revising the product. I don't doubt that
there are good reasons why a documented product keeps
changing enough to need new docs, but it's worth noting the
many moans we keep encountering about (for ex.) Microsoft
Word. The philosophy of "keep changing the features and to
hell with stability and performance" attitude is common
nowadays, and it leads to the "garbage out" part of the
acronym: keep revising the docs just to keep up. Just what
are we espousing here? Worth a thought...
--Geoff Hart @8^{)} geoff-h -at- mtl -dot- feric -dot- ca
Disclaimer: Speaking for myself, not FERIC.
