"isolveproblems", really?
Decisions that eroded trust in Azure – by a former Azure Core engineer
341–350 of 697 posts
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#342The post is so dramatized and clearly written by someone with a grudge such that it really detracts from any point that is trying to be made, if there is any. From another former Az eng now elsewhere still working on big systems, the post gets way way more boring when you realize that things like "Principle Group Manager" is just an M2 and Principal in general is L6 (maybe even L5) Google equivalent. Similarly Sev2 i…
Yes it's easy to critique any large system or organisation, to then go over everyone's head and cry to the CEO and Board is snake like behaviour especially offering you self as the answer to fix it. OP will be marked as a troublemaker and bad team member.
Maybe. That would be a dent in the shiny culture of trust Microsoft is proud to run on, though.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#343Earlier quoted context omitted.
> I submitted several bug fixes and refactoring, notably using smart pointers, but they were rejected for fear of breaking something. And that, my friends, is why you want a memory safe language with as many static guarantees as possible checked automatically by the compiler.
I was waiting for that comment :) Remember that everybody, eventually, calls into code written in C.
Depends on which OS we are talking about.
I know a few where that doesn't hold, including some still being paid for in 2026.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#344It's a nice read. Thank you for sharing this. > Microsoft, meanwhile, conducted major layoffs—approximately 15,000 roles across waves in May and July 2025 —most likely to compensate for the immediate losses to CoreWeave ahead of the next earnings calls. This is what people should know when seeing massive layoffs due to AI.
I honestly thought this was one of the weaker points of the article. The OpenAI deal almost certainly related purely to GPU capacity, which had little to do with the article. The layoffs would have happened regardless. IMO - churn, and generalization is the root cause. Engineers are thrown on projects for a year with little prior experience, leave others to pickup the pieces, etc. There's no longer a sense of ownersh…
[deleted]
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#345Earlier quoted context omitted.
> Last thing, the final part 6 comes off as really childish, risks to national security and sending letters to the board, really? That struck me too. Maybe i've never worked high enough in an org (im unclear how highly ranked the author of the piece is) but i've never been in an org where going over your boss's boss's boss's boss's head and writing a letter to the board was likely to go well. That said, i could easil…
[flagged]
from a philosophy grad. both these responses are logical fallacies.
1: it's bad, but so is everything else (ad populum, everyone does it so it's ok).
2: it can only be because the author has a personality disorder or psychotic break (ad hominem)
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#346from part 2: > Worse, early prototypes already pulled in nearly a thousand third-party Rust crates, many of which were transitive dependencies and largely unvetted, posing potential supply-chain risks. Rust really going for the node ecosystem's crown in package number bloat
Rust is nowhere close to Node in terms of package number bloat. Most Rust libraries are actually useful and nontrivial and the supply chain risk is not necessarily as high for the simple reason that many crates are split up into sub-crates. For example, instead of having one library like "hashlib" that handles all different kinds of hashing algorithms, the most "official" Rust libraries are broken up into one for sha…
I am sensing a "is-odd" and "is-even" vibes from that approach.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#347For some reason, MS is still doing well. I’m not sure what conclusions I should draw from that, other than big businesses are hard to kill?
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#348My most memorable anecdote from working in Azure is that they had two products named Purview and the internal MS people I talked to never figured out which one I was trying to use.
Astronauts have the same problem now.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#349Earlier quoted context omitted.
if the service is so shitty, why are people paying so much fucking money for it? is microsoft committing an accounting fraud?
Because Azure customers are companies that still, in 2026 only use Windows. Anyone else uses something else. Turns out, companies like that don't tend to have the best engineering teams. So moving an entire cloud infrastructure from Azure to say AWS, probably is either really expensive, really risky or too disruptive to do for the type of engineering team that Azure customers have. I would expect MS to bleed from thi…
Turns out outside companies shipping software products aspiring to be the next Google or Apple, most companies that work outside software industry also need software to run their business and they couldn't care less about HN technology cool factor.
They use whatever they can to ship their products into trucks, outsourcing their IT and development costs , and that is about it.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#350At this point, it’s very clear that people nowadays choose Rust mostly to be part of the cult rather than clearly understanding its shortcomings and advantages over languages such as C, C++. It has gotten to the point that some devs after watching a YouTube video criticizing C++ for two hours, announce C++ the worst programming language. Unfortunately, such people become decision makers at giant tech companies too.