Email or username:

Password:

Forgot your password?
LittleAlex 🇺🇦🇮🇱🇩🇪🇳🇴

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

zdnet.com/article/defective-mc

134 comments
Brad Rubenstein “:verified:”

I nominate George Kurtz for President of the United States.

@littlealex

Seth 🎙️:jawn_sg:

@littlealex not the first time and not the last. Mistakes happen, but this is really BAD!!!!

Rachel Greenham

@littlealex @sindarina hm twice is starting to look like carelessness. let me guess: efficiencies?

Sindarina, Edge Case Detective

@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 😜

Klassiker

@littlealex In IT I would say 'I start to see a pattern there'

Raj Naghee Reddy

@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.

Wayne Werner

@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?

Mike Hicks

@littlealex Someone who has too much money (though I'm sure a lot of it's just on paper from stocks)

David P

@littlealex

It seems George Kurtz, his methods have become unsound....

#Crowdstrike #ApocalypseNow

Lesley Carhart :unverified:

@littlealex He made a bad wish with a genie, and has to pay it back every decade, didn't he?

AlexTECPlayz

@littlealex Everything he touches gets kurtzed(cursed). Call it #kurtzification

Yellow Flag

@littlealex I couldn’t quite believe it but – yes, he was really there. I guess he has lots of relevant experience then. 🤪

✊🏾WiseGuyEddie

@littlealex I'm surprised these Big Companies are using McAfee. Even the computer literate home user immediately uninstalls it for being bloatware.

Thomas Fricke (he/him)

@littlealex

He is the grandson of Colonel Walter E Kurtz, who committed war crimes during the Vietnam war

en.wikipedia.org/wiki/Colonel_

rothko

@littlealex omg no way that's too funny. ("funny like an open grave," my dad would reply)

Robert Wire

@littlealex Oh, neat: crowdstrike.com/about-crowdstr

His prior roles at McAfee, a $2.5 billion security company, include Worldwide Chief Technology Officer and GM as well as EVP of Enterprise.

SighBear

@littlealex nominee for CIA MVP Award for outstanding Availabilty: „G. Kurtz“

DELETED

@littlealex

"I wanted to see how many times I could get away with it and fall up; you wont believe the answer." "living thePeter Principal"

Johnny B. 𓅇

@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 😂

en.wikipedia.org/wiki/George_K

Charles U. Farley

@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.

Mark

@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!

Nicco

@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.

Mark

@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.

Charles U. Farley

@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.

@MarkAB @littlealex

Charles U. Farley

@nicovanmourik Point being, killing or severely harming one or more of your customers is just one of many risks in the risk register.

@MarkAB @littlealex

meriksson

@littlealex was he by any chance working at Panda AV in the late 90’s/early 2000?

Panda had something similar back then.

Infoseepage #StopGazaGenocide

@littlealex Didn't know the names involved, but remember the McAfee incident and that was a comparatively easy fix by comparison.

Ray Jepson

@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!

#latestagecapitalism

gadgetoid

@littlealex someone’s trying to pad their CV to get those lucrative state sponsored contracts!

Wintermute_BBS :verified: ⛔

@littlealex let me guess: his favorite business strategy is to raise shareholder value by downsizing QA?

Patrick

@littlealex well that's a coincidence/record he probably would rather have not acquired.

Daniel Marks

@littlealex Well, as the saying goes, sh$t rolls downhill.

ramin

@littlealex that guy does not seem to take the concerns of employees very serious

Claudio Zizza 🦜

@littlealex If this is connected to Kurtz, then it isn't funny at all, because he still earns more money than everyone who will answer your toot and still would find a new higher paid job faster than the average Joe.

rozodru

@littlealex you mean George "I don't believe in Unit Testing but rather Testing in Production" Kurtz? shocked...shocked I tells ya.

Nismorack

@littlealex if I had a nickle every time Georgr Kurtz was somehow related to a global IT meltdown, I'd have two nickles. Which isn't a lot, but strange that it happened twice.

Andreas Albrecht

@littlealex @alice

Sadly enough, I know a company probably eager enough to hire him.

The supervisory committee will probably give him a bonus next year, because of his great accomplishments in dealing with a really difficult situation for the company in 2024. Could they please pay him by making him owner and CEO of a genAI startup? ;-)

Greengordon

@littlealex

More proof that competence is not a core competency for executives.

From 2010: "Oops, they did it again. Early this morning, McAfee released an update to its antivirus definitions for corporate customers that mistakenly deleted a crucial Windows XP file, sending systems into a reboot loop and requiring tedious manual repairs. It's not the first strike for the company, either. I've got details.”

#crowd_strike #microsoft

gnate

@Greengordon @littlealex
Someday, perhaps soon, Crowdstrike will become as relevant as McAfee is now.

cslinuxboy

@littlealex The first step in securing your computer, is not to install security software.

Michael Crews

@littlealex

From Wikipedia:

"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. On a flight, he watched the passenger seated next to him wait 15 minutes for McAfee software to load on his laptop, an incident he later cited as part of his inspiration for founding CrowdStrike. He resigned from McAfee in October 2011."

EaterOfSnacks

@littlealex Once is bad luck. Twice is a bit of an oopsy.

G

@littlealex and the lesson he will learn from this incident is the engineers are all panicky and in the end it all worked out ok after all. Like y2k was no big deal because nothing happened

irizoris@hcommons.social

@littlealex Kurtz's name is straight out of Apocalypse Now!

Alan

@littlealex With that track record maybe he will become the next CEO of Boeing

Philip C James

@littlealex

According to Wikipedia Kurtz was in charge of Risk Management at McAfee!

Wrt to #Crowdstrike, surely it's 'two strikes and you're out...'? Perhaps Kurtz should spend more time seeking the Heart of Darkness or musing on the imminent Apocalypse?

Seriously, if the company is such a single-point-of-failure threat to the ICT environment world-wide it should be sued out of existence.

0px auto;

@littlealex you could say he is now on his 'second strike'... (at least)

Claus

@littlealex surely he won’t get a big fat bonus now. Right?

Walter Tross

@littlealex
McAffe? Not bad, Affe means monkey/ape in German...

ip6li

@littlealex I nominate George Kurtz for manager of Deutsche Bahn.

originlbookgirl

@littlealex I think they should at least dock his pay.

Linux in a Bit 🐧

@littlealex
Now it's *definitely* "not the first strike for the company..." especially when you learn the name of the new company. :blobcatgiggle:

Christian Lauf

@littlealex New motto: "Design your infrastructure like George Kurtz has a piece of software running in it."

Demiurg

@littlealex LinkedIn version is: "Managed several software companies with global impact" 😂

dark_stang

@littlealex I was in college working in an IT "squad" when the McAfee one happened.

I also remember a windows update (vista?) that would bluescreen any system with an AMD CPU in it.

Lines out the door while fixing those things as fast as possible at the front counter.

TJ

@littlealex
Maybe he should take up a new line of work.🤦‍♂️

John Appel

@littlealex If I tried to put this in a novel, my agent, my editor, and my critique partners would the manuscript at my head.

LittleAlex 🇺🇦🇮🇱🇩🇪🇳🇴

@jappel Yes, because they are not doing such thing they will never make billions!

John Appel

@littlealex Also, sweet baby von Neumann, I was working network security for a global financial when the 2010 incident happened. Thankful I retired at the end of 2020.

LittleAlex 🇺🇦🇮🇱🇩🇪🇳🇴

@jappel I have another 15 years to go... If the retirement age will not be increased again...

PS: Congratulations and I envy you!

John Appel

@littlealex I retired early (56 and a half). Fortunately a) my wife has a very good job with excellent insurance, and b) the mostly-ethical company I worked for had a really, really good 401k that I paid a lot into. Took a big income hit but we’re doing OK. I am very, very fortunate & privileged. Strength to you and the rest still in the trenches.

Alice

@littlealex automated updates are his best feature.

FeralFeminist

@littlealex McAffee is junk and always has been. I hate that it’s bloatware included in a lot of application updates and Windows systems, and I always uninstall it immediately.

Bettina Neuhaus

@littlealex Ah well. The Big Boys will always make a comeback.

Nini

@littlealex I'm sure he'll find a way to ascend upwards without consequence.

Fernanda Foertter

@littlealex the good news is the guy in charge has seen this before.

Nils Skirnir

@littlealex
Shows how fragile all our single point of failure systems are. Also how addicted we’ve b come. Even 10 years ago folks could have had work arounds. Now there aren’t any.

ko kāihe ahau 🫏 :verified:

@littlealex @podfeet What’s even funnier is that, in 14 years, #Microsoft still haven’t architected their OS effectively to handle faulty kernel extensions.

Whiskers

@littlealex Quite a niche skill to have on your CV 😬

SloQlap

@littlealex Back in 2010 during the McAfee fuck up, I came up with the solution to fix the issue at scale for Burger King.

I wrote about it afterwards and found the archived version from my old blog. It ended up getting picked up by /., a UK, and Czech computing magazine.

14 years later and it's the same guy repeating the same mistakes again. Even after saving their bacon, BK didn't convert me FTE from contractor.

web.archive.org/web/2010052002

@littlealex Back in 2010 during the McAfee fuck up, I came up with the solution to fix the issue at scale for Burger King.

I wrote about it afterwards and found the archived version from my old blog. It ended up getting picked up by /., a UK, and Czech computing magazine.

14 years later and it's the same guy repeating the same mistakes again. Even after saving their bacon, BK didn't convert me FTE from contractor.

them#tic

@SloQlap @littlealex An important distinction to the English language website. :)

Mike Pirnat

@littlealex Once is happenstance. Twice is coincidence. Three times is enemy action.

Go Up