Live data from Hacker News

Ask HN: Would a .Net back-end put off potential acquisitors?

news.ycombinator.com

61–70 of 103 posts

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#61

Earlier quoted context omitted.

99% of startups simply will never hit the performance problems you seem to be talking about.

Yeah but its the ones that matter, that do? The successful ones with traction.

Indeed. We thought it was the same and nearly lost two big clients because we didn't see it coming.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#62
post #60

I'd like to raise a related point. While I think it's too early to worry about acquisitions, a .NET stack may put off early employees. Many engineers want to work with "hot" technologies for professional development reasons. For example, I would not work for a company whose stack is built on top of PHP or .NET, regardless of pay. Not because these are "bad" technologies (in fact, they are a lot more stable than the h…

> a .NET stack may put off early employees. Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.

Yes, but it's not about the size of the hiring pool. It's about the "quality" of the hiring pool (HN likes to call them 10x engineers).

I don't have any hard numbers to back this up, but based on personal experience almost exclusively all of the best engineers I have worked with prefer to work with open source technologies and would not touch .NET. One can think of several reasons for this correlation that make intuitive sense.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#63
> If it makes any difference, I am funding this myself initially.

The primary concern, if you are funding this and building this yourself, is getting to market. Each day is coming out of your pocket. Choose the technology stack that gets you off the ground fastest. A suitor is not going to reject your company because you aren't using the "hot" technologies.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#64
post #63

> If it makes any difference, I am funding this myself initially. The primary concern, if you are funding this and building this yourself, is getting to market. Each day is coming out of your pocket. Choose the technology stack that gets you off the ground fastest. A suitor is not going to reject your company because you aren't using the "hot" technologies.

But 'off the ground fastest' is an algebra problem - cashflow rates are what matter, not time so much. So early expensive tools MIGHT be better, considering your rent and grocery bills over time.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#66
post #60

I'd like to raise a related point. While I think it's too early to worry about acquisitions, a .NET stack may put off early employees. Many engineers want to work with "hot" technologies for professional development reasons. For example, I would not work for a company whose stack is built on top of PHP or .NET, regardless of pay. Not because these are "bad" technologies (in fact, they are a lot more stable than the h…

> a .NET stack may put off early employees. Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.

The sheer numbers are for the legions of ho-hum programmers building CRUD data-entry systems for e.g. aluminum can factories. The majority of startup-oriented engineers are a different group and I agree that .Net may be off-putting to them.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#67
post #60

Earlier quoted context omitted.

> a .NET stack may put off early employees. Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.

Yes, but it's not about the size of the hiring pool. It's about the "quality" of the hiring pool (HN likes to call them 10x engineers). I don't have any hard numbers to back this up, but based on personal experience almost exclusively all of the best engineers I have worked with prefer to work with open source technologies and would not touch .NET. One can think of several reasons for this correlation that make intui…

Observer bias.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#69

Earlier quoted context omitted.

Yes, but it's not about the size of the hiring pool. It's about the "quality" of the hiring pool (HN likes to call them 10x engineers). I don't have any hard numbers to back this up, but based on personal experience almost exclusively all of the best engineers I have worked with prefer to work with open source technologies and would not touch .NET. One can think of several reasons for this correlation that make intui…

Observer bias.

Perhaps that's true, but my sample does indeed include quite a number of startups whose stack is built on .NET. Their engineers are usually much less experienced (and are often lacking theoretical foundations. E.g. they know how to use MS tools without knowing how stuff actually works) than those of typical SV startups.

I'm sure there are good .NET engineers out there, but hiring/finding them is more like finding a needle in the haystack.

Re: Ask HN: Would a .Net back-end put off potential acquisitors?

#70
Quite a few of the replies are practical, but unfortunately reality isn't always practical. Instead we often use technology for signaling, and the truth remains that the Microsoft stack (even if you talk up open source equivalents like mono) is an anti-quality signal. This is not judgmental (I have used and abused the MS stack for years), but is observational. And that tendency is often based upon experience -- the bulk of .NET programmers are enterprise inhouse developers usually building dated, poor quality solutions.

This hits hiring as well. Someone mentioned the quantity of .NET programmers, and while this is true the quality is extremely, extremely poor on average. Having had to hire .NET programmers, the best success we have had, result wise, is to hire !.NET programmers (e.g. the hiring process started being about abstract problems that could be solved with anything, etc) and let them loose with C#/etc. If we limited ourselves to the .NET skillset we got tonnes of applications, almost all of which were terrible.

Post reply on HN