4 ms·
>Yes. Because mainstream is what you should select for when choosing your tools. Ease of hiring experienced developers should absolutely be a part of selection
by xor1 8y ago
>Yes. Because mainstream is what you should select for when choosing your tools.
Ease of hiring experienced developers should absolutely be a part of selection criteria, but of course it should not be the only one. What good is it going to do you when you picked Elixir/Scala/Rust over Python/Go/Ruby, you need to hire senior engineers who can hit the ground running ASAP, and you have limited resources/budget?
It's going to be harder to find them (especially if you're not in SF), it's a harder/longer initial learning curve if you hire senior engineers without prior experience, it's going to be harder to find non-seniors, you're going to have to pay more to get what you want...the list goes on.
- mirceal 8y agoa senior developer, by definition, will hit the ground running with mostly anything you use. that's the senior part in senior developer. also if you believe that people need years of use to be good in any language/tools/framework you need to figure out how to attract better people. also, the question you need to ask yourself is: do you want to build something with a technology you've selected and think it's the best or do you want to have someone that can pick the right tool for the job pick the tech? sometimes, not building something or various parts of something is more valuable that building something that you don't need fast.
- xor1 8y ago>a senior developer, by definition, will hit the ground running with mostly anything you use. that's the senior part in senior developer. a senior developer also gets to be picky in what stacks they want to work with. usually it's what they are familiar and comfortable with, or something similar to it >also if you believe that people need years of use to be good in any language/tools/framework you need to figure out how to attract better people. even the best engineers have ramp-up time when starting a new job that involves a new code base. that ramp-up time is increased significantly when it's a language that they aren't familiar with. feel free to convince me otherwise, im all ears >sometimes, not building something or various parts of something is more valuable that building something that you don't need fast. what about when it's not?
- opportune 8y agoI don't think it makes sense to group Scala with Elixir and Rust because it interfaces so easily with Java and is used a lot for Spark applications