“uhm you’re only speculating when you say the embarrassing global outage at the company that infamously fired a bunch of its employees to go all-in on AI, is due to AI” it’s fascinating that we’re not allowed to speculate about the fucking obvious thing that microsoft will never confirm nor deny because it’d cause a massive amount of liability and destroy their company
@davidgerard @zzt Maybe they prompted it wrong? 🤷🏻♀️
@zzt : IA is an amazing technology that can do everything but it's never AI's fault.
“fuck you for posting about microsoft just to be an influencer” this is fascinating coming from a proud gnome user and doubly fascinating on mastodon, a platform nobody* is getting paid to post on
* exceptions apply for mutual aid and dark PR campaigns but this ain’t either of those, fucking obviously
“ah ah ah, they denied it’s due to AI/agents” yeah, nobody believes it was due to a fantasy attack by a malicious agent because that only happens when anthropic needs to juice their IPO
we’re saying it’s due to massive amounts of shit code and technical debt produced by the practices microsoft has previously loudly talked about, which include going all-in on AI and agents, and also due to the associated brain drain of firing everyone expensive and having everyone who’s not fired degrade their own skillset with constant LLM use
don’t get it fucking twisted because you want to be a contrarian
@zzt "The outage wasn't caused by AI agents, it was caused by a network configuration change previously that had an undiscovered edge-case".
(BTW this seems to be an underlying cause in most large outages over the years; networks are very brittle and often running too close to capacity)
"But what made the network configuration change?"
"..."
microsoft, a decades-old corporation known to lie about fucking everything, will find the thinnest slice of a statement they can carve out to make you think the recent, unprecedented outage was due to anything except their pivot to AI. all microsoft cares about is preserving their share price and being able to claim they didn’t lie just in case they get taken to court. fucking obviously.
like, I can use my eyes to read the worst incident log I’ve ever seen from any company regardless of its size and come to some pretty fucking easy conclusions:
- this reads like someone frantically prompting an LLM and mildly editing its responses
- this also reads like the people handling the incident have no fucking idea what’s happening (under no circumstances should you write an incident log that reads like you’re frantically flailing and have no idea what’s happening, many hours in)
- HMMM what well-known development and management trend at microsoft involves using a shitload of LLMs, firing skilled employees, and de-skilling the rest??? wow I wonder if that’s related at all
@zzt I remember once accidentally deleting a prod database. It was 24th Dec, we started office drinking at 9:30, and after a 2 hr lunch in the pub. Turns out, I really wasn't paying attention. It was only when someone was topping up my port, and said, "I can't access XXXX/YYY", that my colleague realised I'd deleted 90% of our data. The next 3 hours were frenetic, attempting to restore the previous night's position, while still drinking, and conversing with other drunk people. Wouldn't recommend
@davidgerard @zzt It used to be brilliant, if someone did something daft, and you all worked to correct it
Now there's RCAs pointing the finger....
@zzt I remember reading the report about the three-day outage at Roblox, but it sounded far more methodical in its approach. They figured out what was wrong, why it wouldn't start, and worked stepwise towards a fix. This... doesn't sound like that.
@davidgerard @AndrewMc @zzt wait what incident report are we talking about here?
“uhm you’re only speculating” motherfucker we’re programmers, we used to get promotions for speculating correctly
@zzt I thought Intel put the brakes to all speculative execution
@zzt ah ah ah they did deny it! they swear AI wasn't involved! I still think they're fucking lying