Asklemmy

I actually disagree. I only know a little of Crowdstrike internals but they're a company that is trying to do the whole DevOps/agile bullshit the right way. Unfortunately they've undermined the practice for the rest of us working for dinosaurs trying to catch up.

Crowdstrike's problem wasn't a quality escape; that'll always happen eventually. Their problem was with their rollout processes.

There shouldn't have been a circumstance where the same code got delivered worldwide in the course of a day. If you were sane you'd canary it at first and exponentially increase rollout from thereon. Any initial error should have meant a halt in further deployments.

Canary isn't the only way to solve it, by the way. Just an easy fix in this case.

Unfortunately what is likely to happen is that they'll find the poor engineer that made the commit that led to this and fire them as a scapegoat, instead of inspecting the culture and processes that allowed it to happen and fixing those.

People fuck up and make mistakes. If you don't expect that in your business you're doing it wrong. This is not to say you shouldn't trust people; if they work at your company you should assume they are competent and have good intent. The guard rails are there to prevent mistakes, not bad/incompetent actors. It just so happens they often catch the latter.