[deleted]
Decisions that eroded trust in Azure – by a former Azure Core engineer
71–80 of 697 posts
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#72Earlier quoted context omitted.
I downvoted this comment for sounding like a summarizing LLM, not adding anything substantial beyond the title of the post, before realizing you were the poster and author.
I didn’t know that “subtitle” would appear as first comment.
huh, i didn't realise that's what that does either
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#73from 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
It really is about time that somebody do something about it.
Start with tokio. Please vend one dependency battery included, and vendor in/internalize everything, thanks.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#74I've said it before and I'll say it again. I'm glad rust has good package management I really am. However given that aspect, it ends up forming a dependency heavy culture. In situations like this it's hard to use dependencies due to the amount of transitive dependencies some items pull in. I really which this would change. Of course this is a social problem so I don't expect a good answer to come of this....
Environment is part of the package management. As it stand, it's better than npm only because it is in rust.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#75The 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…
> risks to national security …really? Really. Apparently the Secretary of War agrees with him.
In fairness the SECWAR is hardly a computing expert.
But in this case the SECWAR has been properly advised. If anything it's astonishing that a program whereby China-based Microsoft engineers telling U.S.-based Microsoft engineers specific commands to type in ever made it off the proposal page inside Microsoft, accelerated time-to-market or not.
It defeats the entire purpose of many of the NIST security controls that demand things like U.S.-cleared personnel for government networks, and Microsoft knew those were a thing because that was the whole point to the "digital escort" (a U.S. person who was supposed to vet the Chinese engineer's technical work despite apparently being not technical enough to have just done it themselves).
Some ideas "sell themselves", ideas like these do the opposite.
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#76I just do not understand how Azure has the scale it does. You only need to login and click around for a bit to see this is not a coherent system designed by competent people. Let alone try and actually build something on it.
Who are the customers? Who is buying this shit?
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#77The 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…
> risks to national security …really? Really. Apparently the Secretary of War agrees with him.
To be fair, it's not like Hegseth is a super high-signal source. Hegseth says lots of stuff, some of which are even true!
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#78Earlier quoted context omitted.
Why do you speak about yourself in the third person? Also, after this: https://news.ycombinator.com/item?id=20341022 You continued to work at Microsoft and now there is this takedown? I'm no friend of MS (to put it very mildly) but it seems to me your story is a bit inconsistent as well as the 7 year break between postings.
> Why do you speak about yourself in the third person? When you submit a link to HN, there is an entry field for text in addition to the url. It does not really describe what the text is used for. For links, the content of that field is simply added as the first comment. Someone who is unfamiliar with the submission process may assume this field should describe what they are submitting, and not format it like a comme…
AH! Thanks, that's useful context!
Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#79Re: Decisions that eroded trust in Azure – by a former Azure Core engineer
#80Earlier quoted context omitted.
They should have used the third outlook they didn't know about... Outlook, Outlook (new), and the well-hidden Outlook (classic) that actually works.
That outlook was part of the ablative outlook armor thats suppose to burn off on reentry
Do you have a source for that? I don’t see what impact consumer email software would have with the composition of the heat shield.