Wouldn't Vscode alone can do the trick?
I have been using Vscode previously and could easily find implementions/definitions inside the project by searching.
Never used JB webstorm before, there will definitely be a learning curve with this new IDE. I am not sure the benefits weigh more than the time i have to get used to new IDE.
Thanks for the recommendations. I am already familiar with React, had built a web app at the start of the year. I had some unsuccessful interviews a couple of months ago for a React position and this question came up from the interviewer (it was a senior position) so I posted it here to know what are the approaches other devs are following here.
Right now i am working on a JavaScript/jQuery SPA, a huge app and a lot of bad approaches and coding conventions. I am going to resume with react ecosystem again to update myself with the current industry trends.
Yes that's exactly what i meant by scaling the frontend (maintainability and ability to add new features easily).
What's the tech stack you use on frontend? And for testing which library do you prefer? Do you rely on unit and integration testing only to avoid any regression?
Looks like the book explains the base/core of JavaScript and how some of the concepts work in JS under the hood.
Although it is good to have this knowledge but shouldn't i be focusing on laying the architecture of JS apps and how to scale them? Given that i have been working in the industry for 6 years now.
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?
>if people start to come mostly to me about technical questions over other people in the team, e.g. "how should I write this?", then I'm probably hitting a point where I should move on.
Why is this be a problem for you? Doesn't this imply you are the most knowledgeable in the team (technically)? Isn't this a good thing for a developer?
If I tell them that I am interviewing with other companies it should put some pressure on them and would kind of force them to come up with a decision quickly.
>My $0.01: don't tell anyone if you find a way to automate something (if it's not in your job description).
Isn't this absurd. If you found a way to automate things, shouldn't you just take CTO on call and tell him that you have found a way to improve team's productivity. I think in this way you would be adding value to the team/company, which would eventually be favorable for you during your appraisal.