3 ms·
But we can have both. Make the button yell at you if the circumstances make it dangerous to use it. The fact that they didn't know is a failure of the system, w
by unsafecast 4y ago
But we can have both. Make the button yell at you if the circumstances make it dangerous to use it. The fact that they didn't know is a failure of the system, which should've let them know immediately that the button didn't actually do the thing.
- kayodelycaon 4y agoI agree but I also wonder if there are good reasons more alarms aren’t used. Far worse than the occasional silent failure are too many false alarms. The medical profession has this problem. If you get too many alerts, people ignore them. There was a series of incidents where pilots were routinely pulling circuit breakers to silence takeoff config warnings going off while taxiing. Eventually a plane took off without flaps and a lot of people were killed. Automation is very complex and the solutions aren’t always so straight forward. People forget there is a serious risk of adding an alarm causing more accidents. Should there be an alarm here? Seems obvious there should be and there better be a damned good reason there isn’t.
- deleted 4y ago[deleted]
- unsafecast 4y agoThat's a fair point. I guess attacking the problem from another angle helps then - simplifying the computer UI and minimising the number of situations where an alarm could be warranted in the first place. But yes, this stuff is very complex and I'm (we're?) only judging this from the outside.