Esoteric languages is often a good screener for good devs.
A large talent pool isn't necessarily a positive if you don't spend a lot of effort on your recruiting (mostly filtering) process. It really just increases the risk of bad hires.
A large talent pool isn't necessarily a positive if you don't spend a lot of effort on your recruiting (mostly filtering) process. It really just increases the risk of bad hires.
An example of a language that I could see shifting from one to the other pretty soon is Rust now that it could be a way in to many of the high paying big companies like Google, Amazon, etc.
These companies hire from a different pool than you described.
I definitely didn't have more special accomplishments than 2 typical internships and both were not FAANG.
On the more experienced end of the scale, I'm often surprised to see how many resumes with 3-5 years experience are basically Python-only. This, in the absence of something else in the resume that speaks to domain expertise or something.. its definitely a less exciting prospect to me.
The 2000s version of this were Java-only devs and people who acted as though we didn't need to know how the hardware worked anymore because Java abstracted it away. You see this attitude with some cloud/k8s type dev today.
In both situations, naively.. yes you don't need to understand much about the hardware for your basic implementations.
Arguably once you get into moderate levels of complexity you actually have higher cognitive overhead because you need to understand how the underlying hardware behaves and how the abstraction layers between you & it interplay..
The AGI/singularity conversation aside of course, which I am not at all interested in having. ;)