RE: Documenting a buggy feature

Subject: RE: Documenting a buggy feature
From: "Kieffer, Barry" <barry_kieffer -at- mentorg -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 1 May 2002 09:45:24 -0700


Sometimes as tech writers we see ourselves as the truth police, sometimes to a detriment. There are plenty of bugs that I have documented due to an over-zealous developer's demands that might have been best left undocumented. 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.

Where do you as a technical writer, and development team member, and possible stockholder, draw the line?

.barry.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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

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

---
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.


Follow-Ups:

Previous by Author: RE: Study: Internet Explorer Dominates the Web
Next by Author: RE: Study: Internet Explorer Dominates the Web
Previous by Thread: RE: WORD updating Ole-linked and embedded graphics
Next by Thread: RE: Documenting a buggy feature


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


Sponsored Ads