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: writing around desgin flaws From:Sue Heim <SUE -at- RIS -dot- RISINC -dot- COM> Date:Wed, 15 Nov 1995 09:10:56 PST
Tammy Hale wondered how we write aaround design flaws (those serious
flaws for which there is no logical explanation and no way to get rid
This is said only partly tongue-in-cheek, but write it as an
"undocumented feature." If that doesn't work, ignore it. And if all
else fails, ignore it in the written docs and add it to the
readthis.txt file (of course, this only works for software docs) as a
"known problem" and don't mention anything about fixing it or a work
around (it's just flat a known problem).
Don't ya just love our jobs? <grin>
Research Information Systems
Carlsbad, California USA
Email: Sue -at- ris -dot- risinc -dot- com