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 design flaws From:David Blyth <dblyth -at- QUALCOMM -dot- COM> Date:Thu, 16 Nov 1995 11:01:45 -0700
Tammy Hale asks...
>I'm interested in how people write around serious flaws for which there
>is no logical explanation.
I once very carefully documented a serious bug then made sure to place
that section of the material in an _obvious_ place inside the document.
I placed the workaround in the same location. In this case, I justified
my decision because the bug happened at the tool's core - and I was merely
loudly advertising the core behavior of the tool (It didn't work).
My idea here was to embark on a not-so-subtle campaign to get the bug
fixed. Alas, my fundamental obstacle was that no one used the tool in the
first place. Still, I must confess that yes, this did feel REAL GOOD!
David (The Man) Blyth
The usual disclaimers apply - I don't speak for QUALCOMM, they don't speak