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:writing around desgin flaws From:Tammy Hale <tammyh -at- FGM -dot- COM> Date:Wed, 15 Nov 1995 08:44:41 -0500
The recent thread about writing for beta releases made me wonder how other
technical writers write around design flaws. I'm not talking about stuff
that will be corrected before the final version goes out the door, and I'm
not talking about a few bugs in a program. I'm interested in how people
write around serious flaws for which there is no logical explanation. And,
for the sake of discussion, let's assume that there is no way to get rid of
these design flaws.