Software Bug Accountability
Discussions debate whether major software bugs and failures should be blamed on individual engineers' mistakes or systemic process flaws, emphasizing lessons learned and prevention over personal fault.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It's a bug. Bugs happen. Systems are still systems whether they deal with people or code.When big bugs happen, we evaluate why, and improve the system so it performs better next time. We don't blame people, we focus on what allowed people to make bad decisions. In this case, it sounds like a bad decision making process that needs a patch.
such a bad take. as a software engineer thing like this happen all the time. no matter scale we will screw it.what steps we can take is that it's now a lesson to make it more caution when we went into that path.
Wouldn't be surprised if some overworked engineer made a mistake.
This is the correct reason. Add security audit (internal/external) as well. Don't blame the developers. Blame the process. There will be days on which even the world's smartest person makes mistakes.
Yes, and I'd argue this was beyond a simple "mistake", it's borderline negligence for anyone but a very junior engineer: https://archive.vn/oxbckEDIT: that link isn't working, but here is a screenshot: https://imgur.com/4lyElZI
Can't blame a rogue junior engineer if that happens.
Nice to see the update and I'm very interested in how many people they determine deserve compensation, and why them (if there is any distinction between severely affected and no-big-deal effects). The error seems "basic"...in the sense that everyone who knows devops knows how to prevent it, but according to their account, the circumstances were extreme (plus, it was the holidays) and so mistakes were made. Just like how only a seemingly moron of a surgeon could operate on the wron
I think it's pretty clear that this was a software oversight, and as soon as a human got involved, the situation was resolved.
This is a software screwup. It's buggy software due to rush to market. I hope they do an analysis of the whole project. We can all learn from it.
I haven't read all the comments on these articles, but I haven't seen anyone claim that the bug shouldn't have happened, that anyone should lose their job, that no one "good" makes those sort of mistakes, etc. But this was a bug that lasted long enough and irritated enough customers that one of them finally diagnosed and seemingly fixed it without ever looking at their source code. That's one hell of a process failure. And splitting hairs over whether we would feel