Ask HN: Is working on an old front end stack going to hurt my career

[2bor-2n]

I am working on a SPA for the last 6 months. The frontend stack is jQuery and vanilla JavaScript for the most part.

The product is actually good and the code base is huge. Most of my time goes into identifying and fixing bugs, I also get to work on new user stories but since I am new on the product I am mostly assigned bugs and doing testing so I can get familiar with the product. The good part is I got to learn core concepts of JavaScript like OOP in JS, how prototypes work in JS etc.

React and other frontend frameworks are all the rage nowadays and I am afraid if I keep working with the old stack and don't update my technical knowledge in line with new industry trends then it's going to hurt my career in the future.

I am confused about what to do, should I start looking for a job where react or some other framework is being used on the frontend or keep on the current job for now?

[austincheney]

If you are planning on interviewing at other companies then the answer is an astonishing YES.

I have discovered this myself in recent interviews. If you are a front end developer expect to know React and expect to be interviewed by a supposedly senior developer who hasn’t touched anything in the front end outside of React.

This is so prevalent (and I have no interest in React or other frameworks) that now I immediately attempt to disqualify myself from any position brought to me by mentioning I will not interview with React. This has saved me a lot of time and disappointment.

Strangely I have also observed tremendous interest in TypeScript at just about everywhere, but TypeScript experience is irrelevant if the company is not already actively writing code in it. If a company mentions anything TypeScript keep this mind so that they aren’t wasting your time.

[brudgers]

Do your coworkers, subordinates, and management chain like you? The worst harm you can create in your career is being someone who people don't want to work with in the future.

And the best thing is to have a professional network of people who would hire you in a minute if they could. It multiplies your odds of getting a great job when you are not just another random application in a stack of applications.

Good luck.

[thanatos519]

On the contrary, it sounds like you are learning the basics which will allow you to understand the framework of the month. Keep your current job until there is nothing more to learn there.

[rudasn]

Changing jobs because of the tech stack doesn't sound like the smart thing to do (you know, unless the teck stack is the root of other problems).

As others mentioned, if you are learning new things and you like it so, you can learn react (or whatever) on the side.

FWIW I would prefer a front end dev who has worked with vanilla js extensively and has real experience with the basis over one who has only worked with react or some other framework (if that's the only metric being used to assess their abilities).

[kypro]

Probably a bit. Companies and recruiters will usually look to see if you have a good skill match, especially for more senior roles and having no experience with a modern frontend framework will often be seen as a negative.

If you're strong with JS and have experience writing ES6 code with something like webpack as a module bundler then I think you would be considered. Vue and React honestly aren't that complicated, there are a few things you'll need to learn like how to manage state, lifecycle hooks, etc, but if you're a good dev these things won't take you long to pick up.

If I were you I would work on some projects outside work so you can demonstrate you have at least some familiarity and competence with a framework like React. Although what I usually do when I want to learn a new language is look for a small project I can do at work with that language. Could your company use a new dashboard for something? Could you create some standalone documentation in React? Look for something simple and which is independent of your existing tech stack. It's a little cheeky, but it just tends to look a little better if you can show you've been paid to do something.

I wouldn't quit your job if you're enjoying it and happy with the pay though, just try to find a way to ensure you're not falling behind. Also keep in mind your employer should be aligned with your interests in keeping up to date with the latest tech as it benefits them to have experienced devs. Don't be afraid to advocate for modernising your tech stack and upskilling your devs!

[codingdave]

Knowing vanilla JS and old ways of working are helpful to understand the needs that made React and other frameworks come to be in the first place.

If you really want to learn React or something else, then do it - learn React on the side, or try re-writing the jQuery front-end to React. Or try bundling the jQuery app with webpack to learn those pieces of the puzzle. You can even bring React into the jQuery app and re-write one widget at a time. It would increase the app size, so there are definite downsides, but then you could both keep your job and move forward on tech skills, while slowly modernizing the app.

Basically - get creative. This is not a one or the other decision. At the same time, be careful if you do re-write to React - don't put your learning curve directly in production.

[trcarney]

In my experience, no with the caveat that you have projects that show a basic understanding of the framework the employer is looking for. I have moved from an embedded engineer to a cloud engineer with just projects and embedded work experience. A good employer should look at your work experience as experience with engineering principles and processes. Then they will look at your projects to see that you have at least a rudimentary understanding of the framework.

This may not be the case for front-end development but it has been my experience so far.

[sdevonoes]

You can pick up React in a month. Same goes for any other popular JS framework. If you are applying for jobs where they ask you about specifics framework details, you are applying to the wrong places.

[technobabbler]

It depends on what you're looking for, both in terms of what you use React for and what you expect of the new hire. Basic React can be learned in a day, but there's a lot of hidden complexity regarding state management, contexts, render lifecycles, async, etc. that take a while to get up to speed on. Throw in another framework like Next.js on top of it and it's even more complex.

Not to say any of it is impossible to learn, but it does take more time. It's a lot more complex than jquery because of the shadow DOM and all the timing issues arising from that vs working with real HTML nodes.

All else being equal, I'd definitely choose the candidate with direct React experience who already understands the challenges around that abstraction vs direct DOM manipulation.

[slipwalker]

my 2c: if you have the time and energy, the money is good and the company enviroment is healthy: keep your job, it *IS* important to know to fundamentals. But open a github/gitlab/gitee/gitwhatever portfolio and start some showcase-projects on these trendier frameworks ( i'm a svelte fan, btw ) to keep you coding muscles warm. And remember to link this portfolio on your linkedin page; this way you can have the cake and eat it.

[2bor-2n]

I was looking at some design patterns for JS. I am reading Addy osmani book for that. What i am struggling with is how i am gonna put my learning in to practice. Can someone tell me their approach for learning and implementing advanced JS knowledge outside work?

[plasma]

You may want to take a look at VueJs, it’s a lot simpler than React/Angular in my view and may let you play with it in your current app (to learn a bit about Vue and improve your workflow of complex jQuery <-> DOM updates where it makes sense).

[jyu]

Front end is mostly a young person's game, and most subject to changes in fashionable trends.

React and Vue seem to be the current winners in this space. Prepare to retool yourself in these to pass interviews.

[tata71]

I'll say it simpler than the others: JavaScript isn't "old", focus on quality of work environment.