Let's start by getting the "WTF" out of the way. WTF, by the way.
Now, the CrowdStrike debacle reads like a dystopian novel, some sort of amalgam of Dostoevsky meets Kafka meets Heinlein.
CrowdStrike's buggy patch, itself absurd, unleashed absurdly damaging and widespread upheavals and disruptions to normal life around the world.
CrowdStrike's actions have presented us with _The Curious Case of CrowdStrike vs. DevOps. _ We see that CrowdStrike has something against DevOps.
In one corner, we have CrowdStrike -- a Goliath, publicly traded and now publicly berated -- and in the other, DevOps, a logic-based methodology for producing secure, functioning software.
It would seem that CrowdStrike got a Technical Knock Out (TKO) against DevOps. CrowdStrike definitely succeeded in stomping all over good DevOps.
Yet it was a success of abject failure.
Good DevOps ultimately prevails. It keeps itself and its adherents alive and kicking, developing and releasing software that runs and certainly doesn't cause an easily avoidable global meltdown by preventing hundreds of thousands, millions, of systems from booting up and operating.
Time will tell how CrowdStrike fares after this colossal snafu that fubar'ed so many computers and services.
We'll be dissecting this case study of _The Curious Case of CrowdStrike vs. DevOps. _ for a long time, and into the future, if not the figurative corporate corpse. We'll have to see how the latter part plays out.
DevOps will keep on keeping on. We'll get more and more into refining, explaining, and hopefully applying it.
I look forward to being part of that process. And I hope you'll join me.
Top comments (0)