Earlier quoted context omitted.
> Categorizing yourself exclusively as "a Ruby developer" is a career trap. And a lucrative one at that.
In the short term. And then the entire industry experiences some kind of a technological shift, as it will for many more cycles, and you're jobless as early as the first wave. It's ridiculous how developers mindlessly accept that you should constantly be learning to keep yourself relevant, but keep it shallow by just jumping from one tool to another, instead of encouraging deeper knowledge of generalizable patterns t…
And that’s complimentary with marketing oneself as Ruby/Rails dev or whatever else the market needs at the time.