This six part series (link goes to the first part), written by a former core Azure engineer, is mind-boggling. Microsoft sounds like a dysfunctional company whose software is dangerously unreliable

(I mean, more so than it has been historically)

https://isolveproblems.substack.com/p/how-microsoft-vaporized-a-trillion

How Microsoft Vaporized a Trillion Dollars

Inside the complacency and decisions that eroded trust in Azure—from a former Azure Core engineer.

Axel’s Substack
Microsoft rushed Azure out of the gates under intense competitive pressure. Corners were cut. Fundamental principles of reliability and operational simplicity were quietly abandoned.
Meaning all this came straight from the top. "Intense competitive pressure" is self-induced.

Fortunately this kind of thing, rushing software out the door under self-induced competitive pressure, doesn't happen anymore. Organizations have learned their lessons about the perils of operating this way. (/s)

Layered on this chaos was an Azure-wide mandate: all new software must be written in Rust.
LOL

On a more serious note: LMAO

On top of all that, the org had a hard commitment to deliver the already long-delayed OpenAI bare-metal SKUs that had been promised for years. This work started around May 2024 with a target of Spring 2025 and was led by a Principal engineer who had evidently never tackled a task of that scale.

Fast-forward to March 10, 2025: OpenAI signed an $11.9 billion compute deal with CoreWeave for model training and services.
This detail really struck me. Microsoft's deep internal dysfunction drove OpenAI right into the outstretched arms of Datacenter Enron.

An unbelievable series thanks for sharing. I feel like @[email protected] could make quite a bit of hay out of this one.

@davidgerard @prietschka @[email protected] @baldur

@prietschka Does any of this surprise you at all? Sounds like peak Microslop behavior to me.