Yeah, something this big is absolutely not one engineer’s fault. Even if that engineer maliciously pushed an update, it’s not their fault — it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.
And I actually have some amount of hope that, in this case, it is being recognized as such.
I really don’t want to be the guy responsible for this fuck up
For a company this big it would also have to have gotten past a code review and QA team, right? … right? …
And who pushes out production updates on a Friday!
We do.
“If something goes down over the weekend, fewer people see it” - my leadership team.
I guess Asia can report the problem on Sunday and I’ll get a nastygram and fix it that afternoon.
“Security”
Of course, of course. This is how these things are always done.
This is an industry wide issue. This is just the first symptom.
Yeah and that means they won’t nail some poor schmuck to the wall over this?
Yeah, something this big is absolutely not one engineer’s fault. Even if that engineer maliciously pushed an update, it’s not their fault — it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.
And I actually have some amount of hope that, in this case, it is being recognized as such.
I agree but they will still blame it all on that one guy.