Friday was a mess for just about anyone who relies on Windows - whether they knew it or not. As Friday afternoon rolled along, the little social media I monitor was filled with ideas on what happened - including wild conspiracy theories, and a whole lot of people with not enough information insisting that they knew exactly how they would have fixed the issue.
The briefest explanation is that Gary (my made up name for the person who introduced the flaw) made a mistake.
It’s a Testing Issue
I found it a little cringe-inducing how many folks from the testing community blamed lack of testing or lack of test teams as the root cause. More than one person volunteered to work with crowdstrke to help them improve their testing. I don’t know crowdstrike’s engineering approach, but it’s ludicrous to hypothesize that they didn’t test the change. I have as many details as the rest of you who don’t work at CS, but it’s more likely that they tested the wrong binary, or tested in an environment where th…
