RE: Documenting a buggy feature

Subject: RE: Documenting a buggy feature
From: Diane Evans <Diane -dot- Evans -at- marconi -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 1 May 2002 09:47:06 -0700


Barry says, "If only 0.5% of users might even encounter a certain bug, why
draw attention away from the task and run the risk of confusing even 1% of
the readers who might never encounter the bug? For the rarest of rare bugs,
that is what technical support is for."

I agree. In my former job, I documented many error messages. One would
only show up if everything else went wrong with the device. I wanted to say
something like, "Your device is toast; get a new one." Instead, we settled
for "Call tech support."


Diane Evans
Technical Writer
Marconi Wireless
425-519-2033

Ask for the moon, but settle for its reflection in the pond in your
backyard.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com

Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



Previous by Author: networking handbills, or ???
Next by Author: RE: tutorials vs. instructions
Previous by Thread: RE: Documenting a buggy feature
Next by Thread: RE: Documenting a buggy feature


What this post helpful? Share it with friends and colleagues:


Sponsored Ads