[jampekka]

Exactly. It's weird for me that jobs are so strongly focused on some narrow technology. E.g. "React programmers" or "Javascript programmers" or "Python programmers".

When you know the basic "underlying" model, switching from a framework or language to another is not a very big deal. Not much bigger deal than figuring out a new large codebase with a familiar framework/language.

Sure, it may take a few weeks of learning new stuff and being unproductive (or even negatively productive) during this phase, but this is to be expected in any job.

I don't think learning the more fundamental concepts is that hard but it does require some time (and interest) that is not immediately productive. Perhaps due to demands of being productive, as in churning code, all the time gets people (and the industry) to get stuck in such "local optimum".

[heavenlyblue]

Switching frameworks usually implies learning all of the quirks if these frameworks/platforms, which is the long tail of problems

[marginalia_nu]

There's something to be said for having a deep familiarity with a language. In terms of just churning out basic tasks like churning out CRUD endpoints it maybe doesn't matter so much, but it's both a force multiplier for productivity and an enabler of building something altogether less trivial.

Arguably a lot of the ways modern software sucks is a direct consequence of developers not understanding the tools and languages they're using. It's a bakery that bakes bread by scraping the toppings off frozen pizza.