Space Shuttle crashes and the subsequent Document Analyses have been a staple in Technical Communication. The last Shuttle breakup (and I would contend, the gradualness of the breakup and the horrific possibilities) has bent the typical Shuttle risk analysis. Seems that the pressures are starting to wear on the engineers:
"Schedule matters," he said. "It shouldn't matter to the point of causing people to do dumb things or to take ill-advised actions.... We want to launch Discovery when we can because the completion of the international space station depends upon an expeditious launch schedule. We don't want to launch it sooner than we can."
Tech Comm teachers often take the "look at the moment it went wrong in slow motion" approach, which distorts the "rock-and-hard-place-in-real-time" reality that makes ethics and representation so much more challenging. I would like to see our community create Wiki case-studies that integrate these newer iterations into the narrative. See the strand chronologically would change the way that we teach this stuff--at least in my opinion.
Read more >>
No comments:
Post a Comment