Live data from Hacker News

The Day AppGet Died

keivan.io

151–160 of 566 posts

Re: The Day AppGet Died

#151
post #108

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 pe…

> 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".

Re: The Day AppGet Died

#152
post #108

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 pe…

It's a bit lame to say recruiting must have dropped the ball. If you've engaged with someone, you're inspired by their technology, etc., etc. then handing them over to recruiting for a rejection is pretty weak.

Re: The Day AppGet Died

#153

Earlier quoted context omitted.

From the article, it sounds like he did pursue. After some interviews Microsoft dropped contact.

Could these be a second side to the story that maybe he didn’t interview well or some other reason?

It would probably sting less if they didn't ghost him. Not giving the benefit of the doubt to Microsoft on this.

Re: The Day AppGet Died

#154
post #12

The story reminds me of Andy Hertzfeld’s Switcher: https://www.folklore.org/StoryView.py?project=Macintosh&stor... The difference is that, in 1984, Bill Gates immediately offered $40k and Steve Jobs offered $100k for plugging a hole in their operating system. In 2020, Microsoft just strings you along on vague promises while they simultaneously rip you off.

I love how those stories of the early years are so different from what I think of looking at companies today - > Jeff picked me up at the airport, and we drove to Microsoft's main building where we were joined by Neil Konzen, a talented 23 year old who was Microsoft's main systems programmer on the Macintosh. I knew Neil from his days as an early Apple II hobbyist, when we collaborated on adding features to an assemb…

Neil Konzen's P.L.E. (Program Line Editor) helped make my early days of Apple II programming bearable. It later was expanded into GPLE and published by Beagle Bros.

Re: The Day AppGet Died

#155

Earlier quoted context omitted.

From the article, it sounds like he did pursue. After some interviews Microsoft dropped contact.

Could these be a second side to the story that maybe he didn’t interview well or some other reason?

from an earlier reddit comment,

> I'm sure there was a reason they decided to not hire me. Maybe I had a shitty attitude? I don't know. I'm not questioning that. But I think an email letting me know and some credit would be fair to expect.

Re: The Day AppGet Died

#156
post #72

Earlier quoted context omitted.

Out of curiosity, how long the process took until the deal was signed?

I had to go back and look it was a while back, it took longer than I remembered it. The initial reach out was in May 2011. I had some initial conversation with them in May and June, sent them some overview of the company, etc. Then didn't hear back for a while. In December 2011 conversations started back up. By then the company had actually launched a product where they could see my business being useful. I sent them…

Thanks for sharing the timeline. These things take far longer than anyone realizes.

Re: The Day AppGet Died

#157
op, was done dirty. classic move, even SV had an episode on this kinda business. feign, an acquire-hire. and pick the team's brains out. then launch competing product. I think PG had another essay on this too, never talk to business dev folks

Re: The Day AppGet Died

#158

I have a sneaking suspicion that part of the reason for the sudden radio-silence after his on-campus interview is that someone up the chain realized he is also the creator of Sonarr and just nobody wanted to take ownership of that potential liability.

This. Choose your side projects wisely.

or stop attaching your real identity to online identity.

Re: The Day AppGet Died

#159
post #45

Earlier quoted context omitted.

AFAIK AGPL permits linking without disclosing linked code like LGPL does. Meaning they can still distribute it as their own, train models and serve them with a simpler framework. Just can't build services powered directly by it.

AGPL is as strict as GPL. It's just that GPL allows you to modify the source, serve them as a web application and not have to disclose the code. AGPL addresses that by putting code distributed as a web application in the same category as compiled code.

If my web server calls out to AGPL software (such as executing a transform on a PDF using Ghostscript) as an external binary is this covered even though the AGPL code is not directly compiled, linked or modified? I'd assume so otherwise it would be a very easy loophole and code could be firewalled into separate modules but I'm not sure what exact language covers this in the license.

Re: The Day AppGet Died

#160
post #108

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 pe…

It's a bit lame to say recruiting must have dropped the ball. If you've engaged with someone, you're inspired by their technology, etc., etc. then handing them over to recruiting for a rejection is pretty weak.

I totally agree.

It's a totally different world inside a huge company like Microsoft, though. It's massive and its own little world. After working inside for a few years, you start thinking that it's "normal". You see projects start up and get shut down, you see people trying to get into the company, you see people trying to transfer to other teams within the company, you see people trying to leave the company, you see people in the same team for a decade or more, etc. Because of the scale of things, you sort of become numb to a lot of things you see, so I sort of "understand" if somebody just figured recruiting would sort out that someone wasn't the right "fit" for the company.

I don't think this kind of behavior is necessarily the right one, but it's the outcome of a large behemoth made up tens of thousands of people.

Post reply on HN