the smart ones probably do
Comment on CrowdStrike downtime apparently caused by update that replaced a file with 42kb of zeroes
BossDj@lemm.ee 2 months agoSo here’s my uneducated question: Don’t huge software companies like this usually do updates in “rollouts” to a small portion of users (companies) at a time?
umbrella@lemmy.ml 2 months ago
echodot@feddit.uk 2 months ago
Companies don’t like to be beta testers. Apparently the solution is to just not test anything and call it production ready.
JasonDJ@lemmy.zip 2 months ago
Every company has a full-scale test environment. Some companies are just lucky enough to have a separate prod environment.
Norgoroth@lemmy.world 2 months ago
Peak programmer humor
JasonDJ@lemmy.zip 2 months ago
I’m a bit rusty. I’d give it a C++.
expr@programming.dev 2 months ago
That’s certainly what we do in my workplace. Shocked that they don’t.
deegeese@sopuli.xyz 2 months ago
When I worked at a different enterprise IT company, we published updates like this to our customers and strongly recommended they all have a dedicated pool of canary machines to test the update in their own environment first.
I wonder if CRWD advised their customers to do the same, or soft-pedaled the practice because it’s an admission there could be bugs in the updates.
I know the suggestion of keeping a stage environment was off putting to smaller customers.
Dashi@lemmy.world 2 months ago
I mean yes, but one of the issuess with “state of the art av” is they are trying to roll out updates faster than bad actors can push out code to exploit discovered vulnerabilities.
The code/config/software push may have worked on some test systems but MS is always changing things too.
madcaesar@lemmy.world 2 months ago
Somone else said this wasn’t a case of this breaks on windows system version XXX with update YYY on a Tuesday at 12:24 pm when clock is set to eastern standard time. It literally breaks on ANY windows machine, instantly, on boot. There is no excuse for this.