3 ms·

The incident in Hawaii was user error and is a UI design problem.

• jacobush 9y ago
  Take a systems view? People are increasingly in the loop.
• jasode 9y ago
  >a UI design problem. When a military general or Secretary of Defense asks if the 1960s missile warning system is working "correctly", it means it's working incorrectly when the moon is categorized as an incoming enemy attack. Likewise, when a general asks if the 2018 warning system is working "correctly", it means the system is designed incorrectly if the pixels of text on the screen[1] lead operators to trigger the unintended action. Categorizing one error as a "radar error" and another as a "UI error" as if they are 2 disconnected concepts of correctness is missing the point of BCS's essay. When people think of something working "correctly", they want the whole system to work correctly. They will not explicitly enumerate all the subcomponents nor all the subdisciplines such as "UI design". [1] https://twitter.com/CivilBeat/status/953127542050795520 https://twitter.com/CivilBeat/status/953127542050795520
  • tritium 9y ago
    In this instance, the phrase "code that never goes wrong" does not imply recognition of human factors affecting an operational system.
    • alanbernstein 9y ago
      > (Where “wrong result” is broadly defined to include performance bugs, usability bugs, etc.) The author seems to disagree - isn't bad design a usability bug?
• voidifremoved 9y ago
  I would say it is far more of a process and managerial failure. That it was even possible is to me quite damning of project oversight, for allowing the system to get to that stage with such inadequate procedural and UI safeguards.