News for hackers. Stuff that matters.

A comment on Hawaii "button pusher" refusing to cooperate with FCC, internal investigators. Parent comment

Re:Hawaii "button pusher" refusing to cooperate with FCC, in... by pheldagryph on Thursday January 25, 2018 @10:52PM (#16236923)
> How come everyone wants to blame the system.

Because if the system isn't fixed, it's just going to happen again. Surely you're not arguing that the system is without flaw?

[ Parent | on HN ]
Re:Hawaii "button pusher" refusing to cooperate with FCC, in... by krapp on Thursday January 25, 2018 @11:14PM (#16236988)
The system will be "fixed"... by firing the current operator as an example to the next.

Maybe, maybe someone will print out a list of procedures and tape it up somewhere, telling the new operator that they're required to press the correct button, perhaps in bold and underline for maximum effect. But that's probably it.

[ Parent | on HN ]
Re:Hawaii "button pusher" refusing to cooperate with FCC, in... by AdamJacobMuller on Thursday January 25, 2018 @11:35PM (#16237053)
New sign:

UNDER NO CIRCUMSTANCES IS ANYONE TO PRESS THE "SEND REAL ALERT" BUTTON.

[ Parent | on HN ]
Re:Hawaii "button pusher" refusing to cooperate with FCC, in... by pheldagryph on Friday January 26, 2018 @06:27PM (#16243738)
Strange position; you don't think the user already knew they were required to press the correct button? Your solution seems pretty passive aggressive.

Be kinda like putting up a 'your code must compile' signs in a software dev office. Unhelpfully obvious.

[ Parent | on HN ]