The argument that, because there are always new ways/libraries/practices/standards, the years of experience is not so important is wrong. The exp. will give you the habits to learn fast (learn to learn) in a way that you don't care much about that and more experience means easier learning. A dev with Mern stack only is far away from full-stack or senior. You need to learn fast and implement fast - this is what the experienced dev is.
When you learn a new framework, for the example, you just learn a new way to make the same result. After the years, you will know many ways and one is nothing
Well, that's kind of what I'm saying; just from a different direction. An experienced developer will be able to quickly pick up a new framework and implement it; regardless if they've been using it for a year, or just seeing it for the first time. Putting time in to learn the fundamentals is much more important than having x number of years in a specific tech stack: which is moreso what I am criticizing here; that recruiters and HR look for a specific number of years with their target framework; instead of realizing that general development skills transfer between technologies.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The argument that, because there are always new ways/libraries/practices/standards, the years of experience is not so important is wrong. The exp. will give you the habits to learn fast (learn to learn) in a way that you don't care much about that and more experience means easier learning. A dev with Mern stack only is far away from full-stack or senior. You need to learn fast and implement fast - this is what the experienced dev is.
When you learn a new framework, for the example, you just learn a new way to make the same result. After the years, you will know many ways and one is nothing
Well, that's kind of what I'm saying; just from a different direction. An experienced developer will be able to quickly pick up a new framework and implement it; regardless if they've been using it for a year, or just seeing it for the first time. Putting time in to learn the fundamentals is much more important than having x number of years in a specific tech stack: which is moreso what I am criticizing here; that recruiters and HR look for a specific number of years with their target framework; instead of realizing that general development skills transfer between technologies.