In my comment I support domain knowledge experts. In my comment I purposely mentioned erlang because to implement algorithmic efficiency you must have domain e

In my comment I support domain knowledge experts. In my comment I purposely mentioned erlang because to implement algorithmic efficiency you must have domain expertise. "I don't know erlang that well but I'll be damned if I don't spend the time to find out how to properly do M:N with efficient tail recursion." Tail recursion is an efficiency, doing it right in erlang requires domain expertise. Building new features and adding value is business. Someone with domain knowledge in any of the langs will be able to implement those business values in the best possible way. If your business is built with shitty coders doing shitty things you will eventually find yourself in hot shit. Even if it takes 5 years. What comes around goes around. I would take the domain knowledge developer over any monkey anytime. That's your 10x developer. That's who built all that awesome open source stuff you use all day. Not the business feature value guy. He builds businesses that fail 99% of the time. That other guy building that obscure Lang which turns out useful for that niche topic (I.e concurrency) lives on even in concept to build or inspire other langs/ers. You see, that domain expert knows to pick the right algorithm for the right job. He knows the right Lang for the right job. Even if that job is only business value. Long live domain knowledge experts and those who wish to attain it.