Hacker News new | past | comments | ask | show | jobs | submit login

[flagged]



> Refusal to cooperate in a investigation shows the operator messed up. How come everyone wants to blame the system.

> This comes down to accountability. This person wants to collect a check even though he did his job wrong.

> I have no problem sending him/her to gitmo. You terrorized an entire island with your fat fingers. Now time to pay.

This is why judges have to stress to juries that pleading the fifth or opting not to testify is not an admission of guilt. I considered it redundant when I served on a jury, but your comment has changed my mind. I now wonder if the judge should have said it more often.


Not just his comment, but the fact it was at +9 before getting censored. There's definitely a lot of mob mentality when it comes time to find somebody to blame, and that's very dangerous.


Nearly all comments on the linked article share this comment's sentiment, with quite a few asserting that refusal to cooperate means that he deliberately triggered a false alert.

Interesting contrast to here, where most comments agree on blaming the process/system and that shutting up to avoid incriminating yourself is the proper response, regardless if it was an innocent mistake.


HN commenters are usually fairly thoughtful and level-headed. They have other problems (it's depressing how many HNers have clearly never met a poor person), but it's still much better than most comment sections.


There’s a concept in quality engineering called “poke yoke”, pronounced to rhyme with “okay”. It basically means “mistake-proofing”. As an example, if a part is symmetric and could accidentally be assembled off by 180 degrees, add a “key” feature so that it only fits one way.

The core philosophy is that a well-run system should never rely on perfection from the operators. People make mistakes, that’s normal. A well run system actively prevents mistakes and works to minimize the consequences.

A system where the operator clicked one wrong button and thereby sent out a missile warning to millions of people that took 45 minutes to undo — is not well-designed.


"poka yoke"

Wikipedia: Poka-yoke [poka joke] is a Japanese term that means "mistake-proofing" or "inadvertent error prevention". A poka-yoke is any mechanism in a lean manufacturing process that helps an equipment operator avoid (yokeru) mistakes (poka). Its purpose is to eliminate product defects by preventing, correcting, or drawing attention to human errors as they occur.

https://www.google.com/search?q=poke+yoke


> The core philosophy is that a well-run system should never rely on perfection from the operators

A well-designed system, in this case, could be simple enough that it barely requires the operator to be awake.


Like the little tabs on buttons in a game controller?


> 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?


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.


New sign:

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


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.


I hope to God no one's paying you to design user interfaces.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: