I've been in this space long enough to give you one very important piece of advice: - language and frameworks get you interviews, accomplishments get you jobs

I've been in this space long enough to give you one very important piece of advice: - language and frameworks get you interviews, accomplishments get you jobs Note: that advice isn't relevant to FAANG style companies that do algorithm interviews. They usually don't give two sh*ts about your accomplishments and will put you through the same algorithms non-sense they put a fresh grad. It's much more important to be accomplishing something. The problem with chasing frameworks is that you aren't actually focused on what engineers and developers do; solve problems with technology. So yes, you likely aren't growing maintaining an old code base, but it's not because you aren't practicing React. It's likely because you are spending most of your time tackling technical debt. This is a valuable skill in and of it self, but I would say if you are rather junior, aim for a good balance of greenfield and maintenance. It's important to fully grasp every part of the SDLC. Yes that maybe less relevant in today's "agile" non-sense, but it's pretty valuable for you as a professional to understand what the full cycle is. What does it take to get a project off the ground? What does it take to setup a CI/CD pipeline (and btw, these have existed in some form for YEARS)? What does it take to deliver? Why did you choose language/framework A over B? And so on... Really there are some rules of thumbs we've developed as a profession around this: - If you aren't doing something different in ~2 years, you probably want to ask for a new opportunity internally or move - Always be ready to interview, you're likely to get at least a 20% salary increase by doing this - Longevity in a position is only valuable if you like the organization and intend on moving to management or principal engineer type roles Don't focus so much on frameworks and languages unless you want to be a consultant/contractor in that space. And above all else: NETWORK! Build a real organic network of friends and colleagues. This is more valuable than anything else. These are the people who think of you when a job comes along. These are the people who you join or bring to a new organization to do something trans-formative for that place. This needs to be both organic and deliberate. Keep up with old friends, classmates and colleagues. Make new ones at hackathons, industry events, meetups etc. (this is harder, but possible). And above all else have a life. Participate in non-technology things so you don't burn out. Try learning a new non-technical skill potentially in an industry that you might want to work in. Good luck!