Sometimes I find the pigeonholing thing is just siloing and laziness. The last guy did our infra, nobody else wants to learn it, so the trivial thing to do is just hire on a tick-box basis.
I'm at a company now where one guy was the React guy. He left and everyone else was the snooty anti-React type and refused to learn. They ended up re-writing the whole thing from scratch. Couldn't even be bothered to learn enough to hire for it. And the new framework is so niche it's now hard to hire for it.
Hate React if you want but come on guys, it's not a massively complex framework to learn the basics of.
> And the new framework is so niche it's now hard to hire for it.
Why do you need to specifically "hire for a framework"? Wouldn't any front-end developer be able to pick up any front-end framework (unless it's outside the javascript space entirely, and requires knowledge of purescript, rescript, elm, rust, clojure, scala, etc.)
> one guy was the React guy. He left and everyone else was the snooty anti-React type and refused to learn. They ended up re-writing the whole thing from scratch.
React is close to an industry standard, sounds like bad management. Again, you don't have to know React to hire for React, just bring "smart and gets thing done" people onboard and trust them on their word that they can quickly learn anything they need to get it done. Clear responsibilities and goals, trust, swift consequences if that trust is breached.