RE: Cases where bad documentation caused accidents or worse

Subject: RE: Cases where bad documentation caused accidents or worse
From: "Kevin Christy" <kevinchristy -at- socal -dot- rr -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 18 Apr 2002 19:01:14 -0700


Michael said:

>>If you broaden your inquiry from "bad documentation"
to "faulty technical communication" you can find a
horrible amount of stuff. Many air disasters are
attributable to faulty or ambiguous ground-air
communications, for example.<<

Of course, there's the famous space-age gaffe: "I SAID 'LUNCH', NOT
'LAUNCH'!"

(Pat on the back for the first one to get this obscure reference...)

Kevin


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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: RE: WORD issue solved
Next by Author: RE: Goodbye TECHWR-L (fwd)
Previous by Thread: Re: Cases where bad documentation caused accidents or worse
Next by Thread: Goodbye TECHWR-L


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


Sponsored Ads