zlacker

>>lostms+(OP)
This was definitely not a great experience, but my hunch is what happened is some higher ups decided no, they don't need to hire you, the original team tells recruiting to notify you, recruiting drops the ball somehow, team goes on with their lives believing that you were told they were no longer interested, and everyone (except you, since you never got notified) believed the whole thing was resolved.

The original people (not recruiters) who reached out to you should've connected after the decision was made. They probably figured the recruiters would do their dirty work, so no need to engage.

Full disclosure: I worked at Microsoft for over a decade, so I know how slow and lumbering it can be. I bet some emails were missed and people didn't follow up because "they had a lot of other things they were tracking".

>>allenu+2o
> some higher ups decided no, they don't need to hire you

Total misjudgment on their part. Thanks to this one HN post they already lost in terms of developer good will way more than his potential salary would be.

Every time anyone who uses WinGet, who read this, will think 'oh, yeah, that's the tool that Microsoft build their version of behind original author's back, while stringing him and ghosting for few months".

>>scotty+Qt
Yes. Microsoft really dropped the ball on this one.

So much of what Microsoft has been doing — GitHub, .NET Core, NPM, Visual Studio Code, Windows Subsystem for Linux, etc. — has been to build goodwill with “developers! developers! developers!” Taking the resources to do an acquihire (or hire + bonus) right is small relative to the PR hit.

>>divbze+tI
Exactly. All the things you mentioned are great, and a sign that after decades of being insular, blindly corporately evil, Microsoft started becoming worthy of interest.

And when I first heard about WinGet I though, "Yay! They continue to catch up to the place where developers are! Good for them!", but then this surfaced.