5 ms·
The fewer users a language has the longer it'll take to hire someone, which means there'll potentially be a long wait for what your team can deliver. If you're
by onion2k 9y ago
The fewer users a language has the longer it'll take to hire someone, which means there'll potentially be a long wait for what your team can deliver. If you're a startup a long wait before delivering means you'll run out of money and shut down. If you have a choice, factor hiring team members very highly in your tech stack choices.
- MichaelMoser123 9y agoSome of these languages might come with some inherent advantages that give you an edge over the competition (like memory safety in rust). If the founders are well versed with a new technology like this than that would give them the edge. The problem is that it needs some serious backing for a prog language project in order to become a contender in this game. It is far more than a weekend project (+the founders seeking to apply this knowledge should be well versed in the subject matter) It might be that the end of 'moores law' will make such factors more important to the success of a project, more competition and a smaller margin will lead people to look for other differentiators, so to speak.
- AnimalMuppet 9y agoSome of these languages might come with some inherent advantages that give you an edge over the competition in certain situations. So, use those languages in those situations. Every programming domain has its yak-shaving aspects. Use whichever language and libraries that minimize the yak shaving, so that you can get on with what you're really trying to do.
- opk 9y agoNo, just hire a "programmer". It really doesn't take long to get up to speed in a new language and can make it more fun, adding to motivation. In any other profession job adverts don't specify the exact make and model of tools being used so why is it always required with programming?
- krapp 9y ago>No, just hire a "programmer". It really doesn't take long to get up to speed in a new language and can make it more fun, adding to motivation. It doesn't take long to learn the absolute minimum of many languages, but that might just give someone just enough knowledge to be dangerous, not useful. I would not, for instance, assume that my knowledge of javascript more or less prepares me to write banking software in COBOL or drivers in C, even if javascript and C share a lot of common syntax. > In any other profession job adverts don't specify the exact make and model of tools being used so why is it always required with programming? Because "programming" is not the profession. Programming specific applications in specific languages that meet specific business needs is the profession - and the necessity for domain knowledge beyond the bare minimum required to produce correct syntax is always more important than the language itself.
- sheepmullet 9y ago> and the necessity for domain knowledge beyond the bare minimum required to produce correct syntax is always more important than the language itself. I can't help but feel you are agreeing with the parent poster. In your examples you changed the domain. The parent was talking about the shift in language being the least important factor. It's not entirely true but as a web dev I have written a web app in x86 assembler and cgi-bin without too much trouble. It took longer but I never really felt stuck.
- carlmr 9y agoExactly, it's a classic rhetoric device to destroy an argument by extending it so much that it sounds silly and addressing the silly proposition instead. There are some languages which are very interchangeable where someone from a similar family will be able to get up to speed quickly. e.g. C# developers can be hired for F#/Java/Scala/Kotlin/... positions. They're all GC'd, statically typed and don't require much familiarity with computer architecture. C and C++ devs can be hired for Rust positions, it's both non GC and requires some understanding of what you're doing with your memory, even if Rust is taking your footguns away. Sure, I wouldn't hire a JavaScript developer to do C, because they can do a lot of damage there. But I'd consider a C dev for a JavaScript position, even though I'd have to ask them why they want to do that to themselves. Levels of abstraction might be a better "metric". ASM < C/C++ < ADA, Rust < C#, F#, Java, Scala, Kotlin < Python, JavaScript, Perl < DSLs < GUIs It's easy to move up in the abstraction layers. It's harder to move down, because you have to think about things you haven't thought about before.
- sheepmullet 9y ago> The fewer users a language has the longer it'll take to hire someone In practice that only seems to be true for rapidly growing companies. I've got a list of 30-40 F# devs I could hire in my city. On the other side of the equation my dev team only adds 1-2 new devs/year. In practice we typically take less than a week to fill an opening.
- jcadam 9y agoIt actually seems like it ought to be easier to find a good programmer when you're hiring for one of the more obscure languages like F#, OCaml, Erlang, Clojure, etc. The total number of available programmers may be less, but most of them are probably going to at least be decent (they were self-motivated to learn a non-mainstream language, after all). If you're trying to find a great Java developer (in which case what you're really looking for a great developer who is willing to code in Java for money), you're going to waste a lot more time sifting through legions of incompetent code monkeys to find somebody good (one good screening filter: if Java is the only programming language they know -> reject).
- nathan_long 9y ago> The fewer users a language has the longer it'll take to hire someone, which means there'll potentially be a long wait for what your team can deliver. The number of available devs to hire is $JOBS - $DEVS. Eg, there are lots of Ruby devs, but also lots of Ruby jobs, so you're competing for the few Ruby devs who are on the market. OTOH, there are a small but enthusiastic number of developers using Elixir, Haskell, Rust, etc and wishing they could get a full-time job in it, because there are (currently) even fewer jobs with those languages. You need to factor in not only "how many devs know this language?" but also "how much demand is there for jobs using this language?" If a ton of devs know Language X but most of them hate it, you're not going to have an easy time hiring them.
- toast0 9y agoI've been working in Erlang* for almost 7 years. We mostly hire smart people and give them an Erlang book and help them get settled. I think only one or two hires used Erlang before they worked here, everyone else learned it on the job, myself included. It might be easier to onboard people if our stack was more usual, but Erlang is a perfect fit for our application. * And to work on all the surrounding bits, of course also C and PHP and Perl and even python if it comes up.