jmjm@GossiTheDog intended as a serious question, not snark:
When I push a kernel update to prod I have a gradual rollout plan that lets me canary the change and roll it back, say, before the pager outside the CEOs hot tub goes off.
Did Cloudstrike just not do that, or is there some technical reason (latency between deployment and failure) that this common strategy failed?
All GNU social JP content and data are available under the