I mostly agree here. I haven't read the Doctorow piece. But I've been having a similar conversation within my professional circles. Yes Crowdstrike screwed up. But humans are gonna screw up. We know this. So rather than discussing who to blame, the better discussion is how so many companies found themselves exposed with no way of taking control of what was happening to their systems.
hachyderm.io/@jenniferplusplus…
hachyderm.io/@jenniferplusplus…
Jenniferplusplus (@jenniferplusplus@hachyderm.io)
Other companies have been gutting their operations and security teams. I don't care what they say, the large majority of jobs they eliminated were actually necessary. They've been outsourcing to vendors to cover the gap. Sometimes bad things happen.Hachyderm.io
Marco Rogers
in reply to Marco Rogers • • •Marco Rogers
in reply to Marco Rogers • • •Marco Rogers
in reply to Marco Rogers • • •My mom has been trying to fly back from San Francisco to Atlanta since Friday. Delta Airlines has been totally hosed by this issue. I guess they were deeply invested in windows and Crowdstrike.
But what decision does Delta get to make now? What can they change that won't expose them to a potential Crowdstrike or a similar vendor exposure? I don't think they have that option. The whole ecosystem is set up to shed risk in a way that makes accountability impossible.
jr conlin
in reply to Marco Rogers • • •Yeah, non-tech folk grossly underestimate the complexity and scale big co's like Delta have invested in a given platform. Switching would take decades.
All rooted in basically arbitrary decisions made years ago because some exec bought a sales pitch and went all in on a marketing demo.
Not slighting anyone, though. This crap is hard and impossible to predict. This was (in Delta's eyes) a minor vendor.
Dave Lane 🇳🇿
in reply to jr conlin • • •Marco Rogers
in reply to Dave Lane 🇳🇿 • • •jr conlin
in reply to Marco Rogers • • •@lightweight
Nope. Just drawing from personal experience.
Execs make decisions based on different criteria, and often, don't stay long enough to see the consequences. In this case, I'm betting there was some level of due diligence done, but ultimately it came down to price and features.
Then it got forgotten about since it didn't "catch fire".
Granted, spending money on infra is really hard to justify, so it's usually starved anyway.
Marco Rogers
in reply to jr conlin • • •Richard Johnson
in reply to Marco Rogers • • •@jrconlin @lightweight
Case in counter-point: you could call it broken ticket-toss buck-pass subculture perversely incentivized.
We said "no agent complexity, or if you must, it will have phased and tested/metered roll-outs of changes". We were adamantly overruled. They said "we accept the risk of total revenue outage if this agent breaks catastrophically" and (Catch-22) "you must still ensure no outage" and "you must get budget elsewhere to completely re-engineer your service".
Marco Rogers
in reply to Richard Johnson • • •