Live data from Hacker News

USS McCain collision ultimately caused by UI confusion

arstechnica.co.uk

191–200 of 369 posts

Re: USS McCain collision ultimately caused by UI confusion

#191

A key occurrence during this mishap: 0127 The Officer of the Deck ordered course to the right to course 240T, but rescinded the order within a minute. Instead, the Officer of the Deck ordered an increase to full speed and a rapid turn to the left (port). These orders were not carried out. 0129 The Bosun Mate of the Watch, a more senior supervisor on the bridge, took over the helm and executed the orders. I've witness…

I don't know which one is more bizzare here - the story itself, or the barrage of "this is due to bad UX" comments in this thread. So I guess if this warship fired all its rockets away, "due to bad UX", and destroyed a small nation, I guess the comments would also be about a bad UX. Oh crumbs, the "check status" button was so close to the "start armageddon" button. Perhaps we should submit a meek complaint to Microso…

The problem is that you can't "fix" humans. They'll make mistakes. Aviation is as safe as it is precisely because it moved past the "pilot error! that guy just made a mistake, how can one be so stupid" attitude evinced in your comment.

You have to look at the entire accident chain, and at the entire system, including training, supervision, redundancy, and, indeed, UX.

Re: USS McCain collision ultimately caused by UI confusion

#192

Earlier quoted context omitted.

I’d say it’s the same reason why manual transmission vehicles are still more popular than automatic transmission in some countries. Automatic transmission of modern cars is easier (you can give more attention to the road than having to think about changing gears), gives a smoother ride, is more fuel efficient and causes less wear and tear on the engine. It’s a habit that the organisation is used to, so there is resis…

Automatics are usually less efficient than manuals - the Hydraulic torque converter has to slip to function. That said, the automatic might beat a manual in other metrics.

Modern automatics are almost always more efficient. The biggest is that the torque converter has a lockup clutch during crusing, and often more gears and a near perfect knowledge of when to shift gear.

Re: USS McCain collision ultimately caused by UI confusion

#193

Earlier quoted context omitted.

I can imagine the requirements doc that led to that, where some Pentagon wonk was thinking "What happens if the helmsman is shot? If there's engine damage? If the helmsman is shot and there's engine damage?" and wrote all of those cases in, and completely forgot about the case where the bridge crew gets super confused because they triggered an edge case in the software and have no idea how to regain control of the sh…

Well, it's a warship. In their defense, they really have to plan for people dying and part of the ship being destroyed.

But if it leads to them not being able to steer through a busy area in peacetime where thousands of ships go through every day (many larger than this destroyer), this clearly failed. With this happening I'm not sure if they would've reacted better if they had suddenly been under enemy attack. Would they've been less confused then?

Re: USS McCain collision ultimately caused by UI confusion

#195
post #73

There was a ferry accident involving a similar transfer of control problem in New York harbor.[1] Ferries have a lot of maneuvering modes and directional thrusters, because they do so many dockings, and so they have a more complex control problem. The pilot put the system into a backup dumb mode while in cruise, then changed stations to where he could best see the dock while still in the wrong mode. Rammed the dock a…

I think this whole text, but especially the paragraph about British WWII is a good example of what "Military Intelligence" is about

Re: USS McCain collision ultimately caused by UI confusion

#196
post #147

Earlier quoted context omitted.

The problem is that there's no reason one couldn't design a TV that had both full HD and zero boot time with instantaneous channel switching. The reason such TVs don't exist is simply engineering laziness.

> The reason such TVs don't exist is simply engineering laziness. If your answer to the question "why can't a billion dollar industry provide me with instantaneous channel switching?" is "because they are lazy", you are severely misguided (at the very least!). There are hundreds of extremely talented engineers working full-time on these problems. If the solution were as easy as you propose, the issues would be solved…

> If your answer to the question "why can't a billion dollar industry provide me with instantaneous channel switching?" is "because they are lazy", you are severely misguided (at the very least!). There are hundreds of extremely talented engineers working full-time on these problems. If the solution were as easy as you propose, the issues would be solved.

The answer is never "engineers are lazy". The answer is, the company doesn't give a flying fuck about this problem and will actually prevent engineers from working on solving it, because they can sell you a TV perfectly well with this problem still present, and there's other work for engineers that makes TVs easier to sell than actually delivering a quality product.

Re: USS McCain collision ultimately caused by UI confusion

#197

Earlier quoted context omitted.

I'm sure there's a good reason for the "tradition". Similar to a group of monastic monks following some bizarre ritual which could be done in a more efficient way. Someone from westpoint or the naval academy probably knows..

I’d say it’s the same reason why manual transmission vehicles are still more popular than automatic transmission in some countries. Automatic transmission of modern cars is easier (you can give more attention to the road than having to think about changing gears), gives a smoother ride, is more fuel efficient and causes less wear and tear on the engine. It’s a habit that the organisation is used to, so there is resis…

Cars with automatic transmissions cost more.

Re: USS McCain collision ultimately caused by UI confusion

#198
post #191

Earlier quoted context omitted.

I don't know which one is more bizzare here - the story itself, or the barrage of "this is due to bad UX" comments in this thread. So I guess if this warship fired all its rockets away, "due to bad UX", and destroyed a small nation, I guess the comments would also be about a bad UX. Oh crumbs, the "check status" button was so close to the "start armageddon" button. Perhaps we should submit a meek complaint to Microso…

The problem is that you can't "fix" humans. They'll make mistakes. Aviation is as safe as it is precisely because it moved past the "pilot error! that guy just made a mistake, how can one be so stupid" attitude evinced in your comment. You have to look at the entire accident chain, and at the entire system, including training, supervision, redundancy, and, indeed, UX.

Good UI makes the effort of doing the 'right thing' very little, and the effort of doing the 'bad thing' as costly as possible.

Design (in my opinion) is planning out what good and bad things are for a given tool and determining how to express that through the UI.

Re: USS McCain collision ultimately caused by UI confusion

#199
post #99
post #3

Amazing that someone would design in multiple steering wheels, only one of which is active, and no big indicator to make it super-obvious which one it is. Also amazing that there's a mode where moving a control sometimes controls all engines, sometimes just one.

In my view, on screen UI instead of physical controls is a big factor. If the throttles had been levers it would be instantly discernable if one or both were being moved. This is also why I dislike touch screen controls in cars. I want levers and knobs that give tactile, physical feedback.

Agreed on this. The more important controls should be operable by a suited astronaut, and should also try to express the current 'feedback' of the system state.

Re: USS McCain collision ultimately caused by UI confusion

#200
post #139

Earlier quoted context omitted.

Don't get me started about TVs. When I grew up our family TV turned on in seconds, and pressing channel up/down reacted in tens of milliseconds.

To be fair, you weren't getting near-instantaneous full HD quality broadcasting with DVR support on your TV back then.

Wish I could get that...
Post reply on HN