3 ms·
Introducing something into an existing team and starting a project or team are very different things. But I share some of your reasoning and am curious how thi
by reader_mode 5y ago
Introducing something into an existing team and starting a project or team are very different things.
But I share some of your reasoning and am curious how this actually plays out (I haven't seen any examples so far). One project I worked on, when starting they wanted to do Clojure and they ended up using RoR because everyone was using it and Clojure was a hiring concern. In retrospect RoR fell out of favour, there's a bunch of vacancies for it but it's not very hot so it's hard to find devs and they are forced to take "learn on the job" just like with Clojure, plus you need to compete with a bunch of employers looking to support their projects in now out of fashion stack. I think using Clojure would give them a unique candidate pool and be a hiring differentiator. But that's just speculation. I haven't actually seen how this choice works out in practice.
- kirse 5y agoJane Street (OCaml) and Jet.com (F#, sold to Wal-Mart) are two obvious $B examples. It seems to be more industry-dependent as well.
- anotherhue 5y agoIt worked well early on but once we ran out of F# devs to hire we regressed to the mean.
- dharmaturtle 5y agoArguably that's a "good problem to have". A startup in its early days pretty much requires all its engineers to punch above their weight class. Every company slows down/averages out as once it starts to scale.