[cardanome]

That is exactly the point the article is making though: Do not hire devs that are only happy working in a specific language.

I would add that it cuts both ways: Having developers that are too married to the current tech stack can also cause problems. Sometimes things do need to be rewritten. Sometimes adopting a new tech into the stack can be the right choice and offer competitive advantages. Devs with different backgrounds bring fresh ideas and can help you get out of an local optimum and towards a better global optimum for your goals.

So it is all about balance.

[julik]

What I am getting at is if you don't hire devs _specifically_ who are happy working in your stack you are setting your team up for trouble. What was "I am more familiar with X" during an interview might as well turn into "We should rewrite in X" on the job, and I do feel like this situation should be explicitly filtered against in the hiring pipeline.

But then again, I am biased by having experienced the negatives of the situation.