what should I do to reach from beginner to advanced level js developer?

What should I do to become advance level js developer?

Experts please guide me, tell me the way to improve and resources.

Comments

[Dan E]

Read You Dont Know JS books (all 6) by Kyle Simpson. People overwhelmingly will tell me this is what took them to the next level. I like print editions, but they are also available free online.

[SHARAD SHINDE]

Thanks Dan, I will read.

[Damien Cosset]

If you don't have any inspiration, don't hesitate to read other people's code ;)

You'll see how others people solve problems, or pick up some interesting ways to write code.

[Nested Software]

It's a bit tough to know what you mean by "advanced js developer." However, here are a few ideas for areas to explore in more depth:

• Learn how to develop applications using several different front-end frameworks, such as Vue, React, Angular
• Write a back-end web site/api with Node/Express (or similar)
• Develop a strong understanding of the browser security model, including xss and csrf exploits
• Know how the cooperative concurrency model works in detail in Javascript - look into the details of how the event loop in the browser and node work (also see v8 tasks and microtasks )
• Understand web workers and service workers
• Understand localStorage, sessionStorage, and cookies; know the advantages vs. distadvantages for each one
• Know how to debug and profile js applications for performance, possibly including a detailed understanding of the chrome v8 engine
• Learn how to test your js code, including unit tests, property-based tests, integration tests...

[Guillaume Martigny]

Well, I'm not an expert, but I know one thing for sure:
"You have nothing more to do other than practice."

You know what, don't become an expert. The day you think you know everything, that where you start to wither. Learn every days, follow smart people on twitter, read random articles on dev.to, play around with new JS techs ...

[SHARAD SHINDE]

Practice, that I know but what projects to do or any kind of inspiration that I don't have after doing the 9to5 routine.

[aurel kurtula]

I'd recommend writing tutorials!

you don't need to publish them. Pretend you have a large audience and you need to keep pushing out tutorials. For example, teach them what Nested Software said. They don't need a project they need to learn how to create "api with Node".

The more you do this the easier it will become to find projects.

When I do this, project ideas come easy, I'm deep in code so they are bound to come. What I do with tutorials I've written here is the same idea, mini projects

Find an easy way to take notes, a way that doesn't get in the way (I have this "system", I leave sublime open in the background).

[Guillaume Martigny]

Don't push it. If you don't find inspiration to code, do something else.

Maybe write an article about something cool you've done at work.

Maybe write a fix to that annoying bug on your favorite tool (hoping its open-source).

Maybe write some tests or documentation on one of your old projects.

Each time you find something you can't easily do with existing tools, you have a new project idea.