Live data from Hacker News

The Day AppGet Died

keivan.io

81–90 of 566 posts

Re: The Day AppGet Died

#81

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.

Guilt by association.

This kind of behavior stifles innovation and attempts to limit what people can do.

Re: The Day AppGet Died

#82

Microsoft pretends to want to acquire a product or software and then release their own implementation. The developer was obviously brain-picked for any implementation ideas, as stated at scale. They should have been paying a retainer, or had an offer inside of two weeks. Let this be a warning for other developers.

AppGet is an open source program. Besides, if Microsoft was interested in stealing it, he’d be interviewed at Microsoft Shanghai.

see my comment here,

https://news.ycombinator.com/item?id=23332582

Re: The Day AppGet Died

#83

Microsoft pretends to want to acquire a product or software and then release their own implementation. The developer was obviously brain-picked for any implementation ideas, as stated at scale. They should have been paying a retainer, or had an offer inside of two weeks. Let this be a warning for other developers.

AppGet is an open source program. Besides, if Microsoft was interested in stealing it, he’d be interviewed at Microsoft Shanghai.

You mean you have never been part of an interview or supposed acquihire were you were brain picked? That’s happened to me at least five times already.

There is far more to things than code. Examples: what is your ARPU, why didn’t you do it this way, how many bytes per unit time can you upload this way, where do you see the market going, who is still at the company, what do you think of this type of market?

Re: The Day AppGet Died

#84
post #7

Man, this hurt to read. Keivan’s response is the right one. But I wonder if the arrangements and outcome would have been different had AppGet been closed source. This is just not cricket from team Microsoft.

This isn't secret news, but when you interview at MS there is always a secret / hidden interviewer. This is publicly known information from Cracking the Coding interview. This person is called the as appropriate and you only meet them if you pass all the prior interviews. Per his writeup, he did not meet that person, which means that he most likely did not pass the interview. He also for some reason didn't follow up…

Reminds me of: https://twitter.com/mxcl/status/608682016205344768?lang=en

How exactly could a PM interview process (which is just asking you to walk through a bunch of design scenarios) give a stronger hiring signal than having developed a product the company wanted to acqui-hire? Honestly somewhat insulting that they made him go through a full external interview loop. At most it should have been some informal chats of the sort you get when transferring teams internally.

Re: The Day AppGet Died

#85

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.

In the post, he says the deal was going to be getting hired and getting a bonus as compensation in exchange for him bringing AppGet's code into Microsoft and leading the project. That's a very simple deal in which no ownership of other projects is being transferred.

I'm not a lawyer but I'm pretty sure that hiring someone doesn't mean that you grandfather their liabilities. If that were the case the world would be chaos.

If Sonarr was the reason to reject him then it was done out of complete pettiness.

Re: The Day AppGet Died

#86
post #80

Author here, Because it's sure to come up here is a comment I wrote on Reddit that clarifies somethings, I haven't updated the original article since I'm not sure what the etiquette for updating a highly shared article is. ------ Code being copied isn't an issue. I knew full well what it meant to release something opensource and I don't regret it one bit. What was copied with no credit is the foundation of the projec…

Can you go into more detail about which features you believe were copied?

Re: The Day AppGet Died

#87

Earlier quoted context omitted.

ReasonML is a pretty decent choice. Small learning curve, JS interop, fast compilation, functional goodies. Plus a thing called "Structural typing" that gives you the flexibility of dynamic typing without losing the guarantees from static typing.

Plus, if they are doing front-end stuff, it's my understanding that ReasonML will also output native code, which should theoretically go a long way to making a OS-native app significantly easier right?

Not really, most of the time you're probably interacting with the DOM, which is bound to the browser environment.

Unless you use some framework that also works with native widgets or similar components, you're not getting much advantage.

Re: The Day AppGet Died

#88

1. Release some code under a permissive license 2. Start complaining when companies exercise precisely the rights you have given them

The only complaint I see is the lack of attribution, which is something that is pretty mandatory for open source projects. He's very clear about the situation and that he didn't expect more than he got except for attribution. Did you even read the article?

Re: The Day AppGet Died

#89
post #7

Man, this hurt to read. Keivan’s response is the right one. But I wonder if the arrangements and outcome would have been different had AppGet been closed source. This is just not cricket from team Microsoft.

This isn't secret news, but when you interview at MS there is always a secret / hidden interviewer. This is publicly known information from Cracking the Coding interview. This person is called the as appropriate and you only meet them if you pass all the prior interviews. Per his writeup, he did not meet that person, which means that he most likely did not pass the interview. He also for some reason didn't follow up…

I did, I've since updated the article at the end to note this,

> There was an issue with my travel reimbursement, So I contacted the HR contact and at the same time asked about the Interviews, She told me someone will get back to me about that and they never did. This was on Feb 14th, 2020.

Re: The Day AppGet Died

#90

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.

What's the liability, really?

Let's be honest, if it's a concern they speak up and say shelving this is a condition of employment.

Post reply on HN