TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Consequences of not following the procedures...
Subject:Re: Consequences of not following the procedures... From:Peter Neilson <neilson -at- windstream -dot- net> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 04 Mar 2009 13:41:16 -0500
Victoria Wroblewski wrote:
> Not that it justifies the actions of anyone in this case, but I wonder
> how much the "civilian" attitude of being smarter than the actual
> technology and not following procedures is starting to creep into the
> military as newer/young recruits that more comfortable with new
> technology join. (I've got no personal experience in the military, but
> I believed it to be a place where you followed the orders you were given
> and didn't follow your own spin on the orders.)
At one level, yes, you keep your nethers out of trouble by doing as you
were told. But at some point, especially in combat units, each soldier
is given authority to do what has to be done to accomplish the
objective. "Damn the torpedos [obsolete term for naval mines], full
speed ahead!" You ignore the warning light, either because it's always
on, or because you know that you have eight minutes before the engine
explodes, and you hope you can get the job done in four--the
consequences of failure being loss of your entire squadron. Some parts
of the military (the Marines have the reputation) select and train for
that attitude.
At the command level, a general must be ready to send a group of
soldiers in to die, to achieve an objective. Many returned commanders
prefer not to talk about, "What did you do in the war?" for that reason.
They knowingly ordered men to die for their country. They'll say, "You
don't want to die for your country. You want to make the other SOB die
for /his/ country." But they won't talk specifics. Not the ones I've
spoken to.
Some cultures even teach the soldier to ride or carry the thing while it
does explode. We supposedly don't but I wouldn't bet on it.
Chuck Yeager didn't break the sound barrier by following orders and
procedures. He was technically unfit for duty, with five cracked ribs.
Flight surgeon would have grounded him. Instead, he saw his
veterinarian, got patched up, and flew anyway.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-