3 ms·
When you're choosing a tech stack in a startup there's a very important factor to consider that this article neglects to mention. It's likely, if you have any m
by onion2k 12y ago
When you're choosing a tech stack in a startup there's a very important factor to consider that this article neglects to mention. It's likely, if you have any measure of success or you go down the investment route, that you'll be expanding your technical team quite early. The availability and cost of developers is critical at the beginning. Building in languages like PHP, JS, Java, and to a lesser extend Perl and Python, means you have access to lots of cheap devs. Especially in the case of PHP and JS. Those languages will scale reasonably well to the tens of thousands of users, by which time you'll probably be raising a Series A and you'll be able to afford to shift the important bits of the code to a more appropriate language.
While it might be 'right' to build in C# or Erlang or Haskell or Brainfuck or whatever, if you have to pay a premium to get your first engineer you'll be shortening your runway, and that's pretty much the worst thing you can do. It's much better to build in the 'wrong' stack to start with and give your startup time to get traction. At the end of the day, no one using your product gives a damn what it was built in.
- ehurrell 12y agoAbsolutely true, and so often missed. While it may be true that a good programmer can learn any language the cost of this is time, and nowhere is the phrase 'time is money' more true than in a startup.
- biot 12y ago> Building in languages like PHP, JS, Java, and to a > lesser extend Perl and Python, means you have access to > lots of cheap devs. Especially in the case of PHP and JS. Given that PHP and JS is what Facebook's stack is written in, does this mean that Facebook pays below market salary and they're taking advantage of all those cheap devs who could instead be raking in the money at a C# company?
- onion2k 12y agoI imagine 'coding in PHP' is quite a lot way down the list of requirements to work at FB. There are much more important skills, like being able to write code that works at scale. That isn't the case for most startups - prior experience of the tech stack is right at the top.
- anko 12y agoman, I agree with your recommendation, but strongly disagree with your reasoning. Cheap devs don't pay off. Seriously, I have hired a lot of developers and one good dev (at twice the rate of a cheap one) can easily do 10 times the work, while minimizing technical debt. If you're doing a prototype with the full intention of throwing it away, that's one thing but please don't go cheap. Get less devs and pay them more. As for languages, a startup wants to be cheap. Most of them are doing web stuff. Unless you have a specific need, go ruby or python. People who are interested in either generally are passing on php / javascript for a reason i.e. they're not good languages. Maybe pick go if you want to do systems stuff or performance is critical. The reasons NOT to pick C# are 1) cost 2) lockin 3) flexibility
- onion2k 12y agoIn my experience, in the case of people wanting to work in a startup, cheap usually means 'lots of competition for the job' rather than 'is bad at code'.