The screen that set off the ballistic missile alert on Saturday

Re:The screen that set off the ballistic missile alert on Sa... by WalterBright on Tuesday January 16, 2018 @04:29PM (#16162816)

> But these kinds of mistakes happens ALL THE TIME with "enterprise applications."

Such misteackes in the cockpit of an airliner are deadly, which is why a great deal of effort is expended to prevent such mistakes. Unfortunately,

1. bad UI design is usually only obvious in hindsight

2. doing good UI design is expensive, and not always worth the effort

Of course, I face the same sorts of issues in designing a programming language (D), so this topic is of continuing interest for me.

[ Parent | on HN ]

Re:The screen that set off the ballistic missile alert on Sa... by kelnos on Tuesday January 16, 2018 @06:20PM (#16163827)

> bad UI design is usually only obvious in hindsight

That's only true if you have little or no experience designing or even using interfaces. As someone who has been bitten by bad UI design in the past, I've noticed and called out a decent amount of bad design well before it actually has caused a problem.

[ Parent | on HN ]

Re:The screen that set off the ballistic missile alert on Sa... by WalterBright on Tuesday January 16, 2018 @07:05PM (#16164159)

> That's only true if you have little or no experience designing or even using interfaces.

I'm afraid the history of cockpit design in airplanes decisively shows otherwise.

[ Parent | on HN ]

Re:The screen that set off the ballistic missile alert on Sa... by kelnos on Wednesday January 17, 2018 @08:07PM (#16173737)

I think we can agree that some elements of bad UI are obvious, and others are subtle.

Based on the photos of the screen shown in the article, this one's dead obvious.

[ Parent | on HN ]