4 ms·
What's disturbing is the mindset in the friendly-fire disaster that the OP links to: > Nonetheless, the official said the incident shows that the Air Force and
by danso 11y ago
What's disturbing is the mindset in the friendly-fire disaster that the OP links to:
> Nonetheless, the official said the incident shows that the Air Force and the Army have a serious training problem that needs to be corrected. "We need to know how our equipment works; when the battery is changed, it defaults to his own location," the official said. "We've got to make sure out people understand this."
I hope that's not the mentality of the military today, that special forces operators in the field need to remember UI/UX details of the software they use...rather than the software developer adding in relatively simple safeguards, such as confirmation boxes.
It's also a lesson in how software development and engineering can go awry without close feedback from the audience. There are on-the-field realities -- such as the battery going low -- that even if the developers are aware of, they can't easily predict how the intended user will react in those scenarios...to tragic results, in this case.
- pc86 11y agoWhile I agree with everything you've said, this could very easily have been the opposite problem had they implemented something like that. A squad is killed by enemy fire and we recover the GPS unit with the "Are you sure? Y/N" box still flashing, and a newspaper writes an article about how our military needs push-button solutions and not dialog boxes.
- danso 11y agoYes, I was thinking that too...there really is no "perfect" solution, just a thoughtful consideration of the tradeoffs...my inclination is that this particular "feature" hadn't been discussed enough. To be fair, this is a product that's probably hard to user test, due to the limited number of users and the black box nature of most proprietary military software. Another thing I wonder about: this happened in 2001, an era that IIRC, portable devices were few and sleep/power-down modes were not as well-executed as they are today. Yes, today, if I were to power off my mobile device, then replace its battery, and power it back on...I would expect things to be more or less how I left them (which is a little unrealistic, depending on the application)...but back then, I could see how a developer would think: "Well of course everyone knows system state gets reset when the device is powered down for any reason"
- jerf 11y agoIt's a bit of both... yes, these bugs ought to be fixed in software whenever possible. However, the military can't wait until everything's perfect to deploy, and the users of the technology need to be trained on all the sharp pointy bits in the code. Some of these will be bugs, and some of these will just be that this is military code and it's built to have sharp pointy bits, some of which inevitably can be aimed at oneself. As someone else points out, firing on one's own position is a valid use case in the military. If you can't wrap your brain around that statement... go thank a soldier. Again let me emphasize I'm not saying the software is OK as is. It should be fixed, somehow. But at the same time, the military can't afford to just, say, stop using the unit entirely until then, and wait until all equivalently serious bugs are fixed. Not having the software 'cause it's in the shop can be fatal too.
- yoav_hollander 11y agoRight. Cutting-edge military systems are, indeed, risky business, and one has to balance (as you say) more testing against not having those systems when you need them. This puts a high premium on the efficiency of bug-finding, especially spec bugs of new systems. My intuition is that this could improve by a lot.
- Confusion 11y agoI'm not sure this tragic example is actually a good example. If I replace the battery in my alarm clock, I check whether the alarm is still set, because I know I can't rely on it. If you set coordinates for something as vastly more important as an airstrike, shouldn't it be par for the course that you doublecheck the coordinates if you replace the battery between setting the coordinates and pressing 'fire'?
- tadfisher 11y agoThink deeper: what is the use case for a GPS unit setting airstrike coordinates to its own location?
- Confusion 11y agoA guy here recently got quite an important medal for doing exactly that.
- breischl 11y agoFrom Brian Thacker's Medal of Honor citation: "Then, in an act of supreme courage, he called for friendly artillery fire on his own position to allow his comrades more time to withdraw safely from the area and, at the same time, inflict even greater casualties on the enemy forces." John R Fox's citation: "As the Germans continued to press the attack towards the area that Lieutenant Fox occupied, he adjusted the artillery fire closer to his position. Finally he was warned that the next adjustment would bring the deadly artillery right on top of his position. After acknowledging the danger, Lieutenant Fox insisted that the last adjustment be fired as this was the only way to defeat the attacking soldiers. Later, when a counterattack retook the position from the Germans, Lieutenant Fox's body was found with the bodies of approximately 100 German soldiers." Pretty sure you can find some more if you look. [1] - http://www.cmohs.org/recipient-detail/3431/thacker-brian-miles.php http://www.cmohs.org/recipient-detail/3431/thacker-brian-mil... [2] - http://www.cmohs.org/recipient-detail/2744/fox-john-r.php http://www.cmohs.org/recipient-detail/2744/fox-john-r.php
- hyperpape 11y ago
- dragonwriter 11y ago> I hope that's not the mentality of the military today, that special forces operators in the field need to remember UI/UX details of the software they use...rather than the software developer adding in relatively simple safeguards, such as confirmation boxes. Those aren't mutually exclusive alternatives. Special forces operators (and soldiers more generally) need to understand the operational characteristics of the equipment they actually have. This does not mean that suboptimal UI/UX in military equipment shouldn't be addressed, it should.