3 ms·

I disagree with most of the things in other comments. Working in legacy makes it harder to land a job that isn't related to legacy code. No one cares that you s

I disagree with most of the things in other comments. Working in legacy makes it harder to land a job that isn't related to legacy code. No one cares that you spent x years of your life maintaining some old crap written in a language that went out of fashion. Staying in such a job equals putting yourself at a disadvantage in the future and is not worth it at all unless the job pays exceptionally well... and my experience is that such places actually pay worse. When I look for a job the number one question I ask is "how old is the project" and number two is "what kind of technologies are primarily used". If it's something that's older than 5 years I don't pursue the offer any further.

baron816 7y ago
I agree here. React is not a fad. Its matured and has essentially become the industry standard. My company gets lots of young engineers who don't really know React that well, and it can be a problem. It can be issue even for those with lots of front end experience since they've built up habits and patterns and mental models that don't really make sense any more. On the other hand, I'm thought of as an expert in modern JS and React, so I get all the hard/interesting problems and everyone comes to me whenever they have a question. That's generally a good position to be in career wise. But, really, the benefit of using modern tech is that it's going to make you much more productive especially when we're talking about the front end. A more productive dev is a higher paid dev.