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 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 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.
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.
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.
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.
A well-designed system, in this case, could be simple enough that it barely requires the operator to be awake.
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?
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.
UNDER NO CIRCUMSTANCES IS ANYONE TO PRESS THE "SEND REAL ALERT" BUTTON.
Be kinda like putting up a 'your code must compile' signs in a software dev office. Unhelpfully obvious.