Too funny: In 2010 McAffe caused a global IT meltdown due to a faulty update. CTO at this time was George Kurtz. Now he is CEO of #crowdstrike
https://www.zdnet.com/article/defective-mcafee-update-causes-worldwide-meltdown-of-xp-pcs/
I nominate George Kurtz for President of the United States.
@littlealex that's funny indeed
@littlealex Damn, we're kurtzed
@frankstrater @littlealex Does it take 1 Mooch to become Kurtzed?
@littlealex not the first time and not the last. Mistakes happen, but this is really BAD!!!!
@littlealex @sindarina hm twice is starting to look like carelessness. let me guess: efficiencies?
@StrangeNoises @littlealex Clearly it is to CrowdStrike’s benefit to have a CEO who has dealt with such an issue before, at a difficult time like this
@littlealex In IT I would say 'I start to see a pattern there'
@littlealex @catsalad sadly I remember this and was directly affected by it.
We learned that we needed to split our AV deployments into phases, with a small set of “canary” testers in our earliest TZ specifcally to test for this kind of problem.
Administration was painful but less painful than having hundreds or thousands of machines down.
@littlealex given the impact of CEOs on culture... anyone wanna bet they struggle with blameless postmortems and there's not an attitude of trust within the company?
@littlealex Someone who has too much money (though I'm sure a lot of it's just on paper from stocks)
@littlealex Repeat offender
@littlealex This guy is bad luck!
@pch @littlealex he's good at bad luck
@dirkhh @littlealex ....I should cause some gigantic outages, I guess.
@depereo
Might be worth a try...
It seems George Kurtz, his methods have become unsound....
@pewnack @littlealex I don’t see any method at all
Sounds like he needs to be terminated with extreme prejudice.
@littlealex He made a bad wish with a genie, and has to pay it back every decade, didn't he?
@hacks4pancakes @littlealex sounds about right, honestly
@hacks4pancakes
2038 is going to be fun.
@littlealex
@littlealex Everything he touches gets kurtzed(cursed). Call it #kurtzification
@alextecplayz Kurz in German means "short". Some theories are forming in my head...
@littlealex how will he fail up from here.
@grumpasaurus Moving to the White House?
@littlealex I couldn’t quite believe it but – yes, he was really there. I guess he has lots of relevant experience then.
@littlealex hope he’s preparing 3 letters.
@littlealex failing upwards I see.
@littlealex I'm surprised these Big Companies are using McAfee. Even the computer literate home user immediately uninstalls it for being bloatware.
He is the grandson of Colonel Walter E Kurtz, who committed war crimes during the Vietnam war
Just fooling the #AI
Haha amazing! How did you dig this one up?
@madeindex Painful memories...
@littlealex what grandpa still knew about ;)
@littlealex omg no way that's too funny. ("funny like an open grave," my dad would reply)
@littlealex noooo fucking way
@littlealex Oh, neat: https://www.crowdstrike.com/about-crowdstrike/executive-team/george-kurtz/
His prior roles at McAfee, a $2.5 billion security company, include Worldwide Chief Technology Officer and GM as well as EVP of Enterprise.
"I wanted to see how many times I could get away with it and fall up; you wont believe the answer." "living thePeter Principal"
@littlealex nominee for CIA MVP Award for outstanding Availabilty: „G. Kurtz“
@littlealex from his Wikipedia article:
"Over time, Kurtz became frustrated that existing security technology functioned slowly and was not, as he perceived it, evolving at the pace of new threats"
Yeah, move fast and break things, my ass
@littlealex The bugs I saw working there...
Let me tell you, the vast majority of programmers working for "security" companies are no more qualified than your average programmer to be doing anything security related. And there's not nearly enough review from people who are, if there's any at all.
@freakazoid @littlealex I can confirm this first hand.
@freakazoid @littlealex My wife (former software QA person) complained for decades as her QA people were systematically eliminated in the name of “efficiencies”. “The programmers can test the code as they write it”, they said. And somehow the code always worked perfectly when run with the perfect little test system the same programmers created!
@MarkAB @freakazoid @littlealex ow! This sounds quite familiar to me. Apparently it’s the same everywhere. Our (tiny) company is usually cut out of the project whenever profits are not as high as expected. To be hired back again when the shit hits the fan. In other words: too fucking late to be really effective.
@nicovanmourik @freakazoid @littlealex My small software company was bought by a larger company. For years I tried to stop layoffs of staff who supported legacy products. Those making the decisions had no idea what those people did, and assumed the legacy systems weren’t important because they had never heard of them. I lost the battle about 50% of the time, and usually within a year something crashed because a critical system had not been updated.
@nicovanmourik The thing I realized working for startups is that the thing that's most likely to kill you is being late to market. One startup literally put one of its customers out of business by losing all their data. Now they're a public company storing data for some big names.
@nicovanmourik Point being, killing or severely harming one or more of your customers is just one of many risks in the risk register.
@littlealex was he by any chance working at Panda AV in the late 90’s/early 2000?
Panda had something similar back then.
@littlealex Didn't know the names involved, but remember the McAfee incident and that was a comparatively easy fix by comparison.
@littlealex wow.. looooooooooooool
@littlealex imagine the bonus this guy is going to get when he is fired this year? They could have afforded to QA this 100 times for the cost!