As a technical writer, I have a lot of anxiety about releasing documentation with errors. Sometimes I lie awake and wonder if I should have had another person review the godforsaken diagram I’ve been toiling with for two months. The diagram chases me through my dreams. (And I have reason to believe that I haven’t seen the last of that bastard.)
This weekend, I read Into Thin Air by Jon Krakauer. The book is about Krakauer’s disastrous expedition to the top of Everest during which an unusually large number of people died. At the beginning of the story, the author laments that when he returned from the trip — badly shaken, of course — he had to get right to work pounding out the contracted 17,000-word article detailing the tragic adventure for Outside magazine, who paid for the trip. Under the wire, he bungled some facts and made a major error that he says caused a lot of pain to the family of one of the deceased.
Now let’s discuss what’s worse: falsely representing the events surrounding the death a person who perished on Mount Everest during the deadliest season on the mountain vs. incorrectly labeling an arrow on a diagram in a software manual that 27 people might read.
Perspective. I have some now.