Live data from Hacker News

It Was Bad UX, not a “Wrong Button” in Hawaii

washingtonpost.com

111–120 of 132 posts

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#111
post #76

Earlier quoted context omitted.

>A warning, whether mistaken or not, is not a death threat, and a death threat is not just a complaint. I don't think there is exactly the same crime in all the states of the US, but there is in some states (as well as in many other countries) the crime of "false public alarm". Example, you start crying "Fire!" in a crowded cinema or public place: http://mollolawfirm.com/resources/criminal-law-resources/fal... P.S.:…

There's a difference between crying "Fire!" to willingly cause panic over nothing (ie: intent to cause harm), and a mistake... Text from your first link even says that: > A person is guilty of a crime of the third degree if he knowingly causes such false alarm [...]

>There's a difference between crying "Fire!" to willingly cause panic over nothing (ie: intent to cause harm), and a mistake...

Sure there is a difference, but - again not all states/countries Laws are the same - it may depend on who has to prove that it was a mistake.

And of course it may be classified as an actual crime or as a minor civil infraction.

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#112
post #110
post #104

Earlier quoted context omitted.

A blank round looks totally different from a 'live' round with a projectile.

Don't assume there is just one kind of blank, and don't assume blanks can't kill you. https://en.wikipedia.org/wiki/Blank_(cartridge)#/media/File:... The first bullet here is a blank.

A 'bullet' can't be a blank, as a bullet is a (normally) inert projectile.

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#113

Earlier quoted context omitted.

it's not "terrorism" it's a "terroristic threat" - same root, but different words and very different meaning as commonly used. no one is equating a drunken bar confrontation and suicide bombing, except you.

He didn't equate them though, that was his whole point.

he says he thinks the words mean the same thing to the authorities -- which they do not; that would be crazy.

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#114
post #95

Earlier quoted context omitted.

I'm not scolding the ape, I'm scolding the organ grinder. When a drill deviates from the actions taken in an emergency it becomes a pantomime of little value. I totally agree that the solution should leverage obviation to prevent human error in an emergency, that's what a drill is all about.

> When a drill deviates from the actions taken in an emergency it becomes a pantomime of little value. Sending an emergency alert isn't an action that requires split-second muscle memory. I think slight deviations in the drill vs. the real thing are fine in this case, in order to prevent false alarms. There's no one-size-fits-all solution here, you have to analyze the trade-offs around speed and the cost of a false a…

It hasn't prevented a false alarm, which is why it hit the news... it's interesting that there is a lot of hang up on false negative (false alarm) and very little discussion about a false positive (hitting the test button instead of the real alarm)

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#115
post #12

For all developers asked to design something or not given a design - CSS padding is your friend. Add spacing and then add more. It won't make it a masterpiece but it'll prevent misclicks and make the UI easier to read and understand. Also, use headings like "Amber Alerts", "Weather" and "War". And, use semantic titles like "[TEST] Tsunami" or "ALERT! - Tsunami"

Developers don't design. They implement.

I think the vast majority of software is developed without the handholding of a UX specialist. So they do "design" in those cases, right?

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#117
post #60

Earlier quoted context omitted.

That's a good example. Shockingly poor foresight. It's similar to the "A gun is always loaded" principle. Unless you can tell at a glance that a firearm is not in a ready-to-fire state, you treat it as if it is. People are clumsy and forgetful, and you only have to mess up once. Leaving the live rounds right next to the blanks, in that way, is pretty indefensible. (Ignoring of course that blanks can still kill, for t…

>Unless you can tell at a glance that a firearm is not in a ready-to-fire state, you treat it as if it is That's when you need to treat it like it is the most.

You'd really exercise more caution with a broken-open shotgun than a closed one?

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#118
post #112
post #110

Earlier quoted context omitted.

Don't assume there is just one kind of blank, and don't assume blanks can't kill you. https://en.wikipedia.org/wiki/Blank_(cartridge)#/media/File:... The first bullet here is a blank.

A 'bullet' can't be a blank, as a bullet is a (normally) inert projectile.

Going for the 'technically correct' award, are we?

Yes, the correct term is indeed 'cartridge'.

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#119
Their solution to the problem was to add an additional "BDM False Alarm" entry to the list of alerts which will send out the message that the previous alert was a false alarm and there is no threat.

Perhaps they should also add a "false alarm that this was a false alarm, there really is a threat after all" option in case the "false alarm" option is selected accidentally after warning about a real threat. /s

I don't know how anyone in Hawaii can be expected to trust or take these alerts seriously after this.

Re: It Was Bad UX, not a “Wrong Button” in Hawaii

#120
post #112

Earlier quoted context omitted.

A 'bullet' can't be a blank, as a bullet is a (normally) inert projectile.

Going for the 'technically correct' award, are we? Yes, the correct term is indeed 'cartridge'.

Not really, your entire argument is silly. You should be running through ACTS/PROVE regardless of the state of your firearm or its load.
Post reply on HN