this post was submitted on 23 Nov 2025
229 points (97.9% liked)
Not The Onion
18765 readers
2020 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Assuming they were using threshold cryptography, they could have easily configured some redundancy into the system, e.g. by requiring 3 out of 5 people to decrypt it instead of 3 of 3.
It's easy to blame the one guy for losing the key, but he could have gotten hit by a bus or lost the hard drive in a house fire and they would have been equally as screwed. This is more of a system design failure than a PEBKAC failure.
in complex systems design, you never blame human error. humans are fallible, and if the system doesn’t account for human error then it’s just a matter of time until failure occurs. look for a way to make the system tolerate or eliminate human error
Ah, if only managers understood this principle.
My motto is that "all failures are management failures." But I'm not far enough up the chain to really implement that 😅
idk i fuck up and release buggy code at least 10% as much as management makes dumb ass decisions
And the 10% when you do… you were mismanaged!