> I have had jobs where i was expected to know a particular programming language Which falls under the same thing we are talking about. If you know one program

> I have had jobs where i was expected to know a particular programming language Which falls under the same thing we are talking about. If you know one programming language, you can figure out them all. You'll probably fall down flat when it comes to idioms of an unfamiliar language, but the same can be said around the idioms of frameworks. Many programming languages even include their own frameworks out of the box as part of the standard library, muddying the lines further. As far as this discussion goes, there is no meaningful distinction to be made here. > But if someone is hiring permanent employees on the basis of flavour of the month frameworks, they have no idea what they are doing The ask isn't necessarily flavour of the month. I still see tons of jobs looking for people with experience in Rails, for example. It hasn't been popular for at least a decade. However, from the job seeker perspective only knowing Rails limits to only Rails jobs, even when one knows everything about web development and could just as easily develop a web application in bash if you asked. > and i would advise against working for them. It is not an unreasonable ask, to be honest. Gaining familiarity with idioms is unquestionably the hardest problem in computer science, even above what the familiar joke suggests. While you can start to write code in a new language/framework almost immediately, It can take years to gain the understanding necessary to write great code. That is why businesses shy away from great programmers who don't know the idioms of a particular system adopted within the business.