Vorhies seems to be intolerant of woke tards and DEI airheads. 
In the comments, some users took Vorhies to task for using DEI in a way that suggests DEI beneficiaries are less qualified or sources of error.
Vorhies seems to be intolerant of woke tards and DEI airheads.
Good analysis.
Is this what happens when they tell all those people whose minimum wage jobs have been outsourced to China to “learn how to code”?
So, they forgot to carry the 2.
Well, that explains it all. Never go full null. I took a stack dump this morning.
A simple test done against even a single machine would have flagged this as a "blue screen of death" problem. For far too long, updates are being pushed against in-use machines without prior use against test machines. If you can't get past the test machines, you don't launch it against in-use machines.
p
Zach needs to learn how to spell “privileged”. He badly butchered the spelling.
I’m inclined to believe that this was a White Hat operation against a well known evil actor.
I am hearing they let go of a bunch of DEI programmers 2 days before this happened.
this is all SOP in the software development world ... there are tools such as valgrind that identify such potential errors and vulnerabilities. It’s puzzling from a professional perspective how such made it to production and reveals poor methodology that behooves anyone expecting such amateurish production model to grant authority as a “security” provider.
Once all the lawsuits and settlements finish up there will be no more Crowd Strike..I am a Sr Admin at a major bank and sure cost us in labor and outages....
As a programmer I have heard about null exceptions. Never created one myself. Seriously never one this bad.
Doesn’t this explain what a complete crap-show our supposed awesome technology is? 1 security update from a single company can take down so much stuff around the globe. Horrible.
This is Geek to me. 🫤
Do today’s programmers even desk-test their own code? In the early days, the programmer was expected to have a stub app on his machine wherein he crafted the code with all the requisite inputs and outputs including all headers and library linkage (to eliminate naming collisions), compiled, linked and TESTED (bounds checks, min/max parameters, unterminated strings, etc.) before submitting it to the dogfood repository. There it was given the evil eye by several highly-paid (and super-stressed) mercenaries, then compiled and linked into the dogfood testbox where it was given a fairly thorough hands-on BEFORE it was even NOMINATED for the production build. It would have to pass a couple of code reviews AND a functionality review before being piped into production. Each line of code had about ten sets of eyes on it before a customer was allowed to test it. But that was then (the 1990’s), and this is now.
Dividing by zero works!
