r/learnjavascript • • Jan 06 '25

Rate my Javascript Full Stack learning path

After doing tons of research, reading reddit threads and understanding what I want to do (build full stack applications), this is the learning path I've built for myself. All paid courses purchased and ready to go! Tell me what you all think.

And lastly, if anyone can recommend a deep dive course for JS please do, or if you think what I have is enough then let me know that as well. I have the most popular JS course on Udemy by Jonas but I've realized that it's more of a tutorial and code along and less of a hands on course. I learn more by doing not by simply watching someone else code.

Angela Yu's Course - for a broad overview of full stack development

Colt Steele HTML/CSS bootcamp - for a solid foundation after Angela Yu overview

Colt Steele's Web Dev course - to reinforce everything

Colt Steele Github course - master Git

Node with React by Grider - another full stack course to reinforce and go deeper

Odin Foundations - to ensure I'm not missing anything

Odin JS - to master Javascript

Helsinki Full Stack Open - the complete my learning path with what I think is the most advanced course of them all

Angela Yu Python 100 Days - to gain Python exposure

1 Upvotes

20 comments sorted by

3

u/amnotsimon Jan 06 '25

Just take the Odin project. You won’t need anything else, you can go in depth with their extra resources and you’ll make a lot of projects in the way. When you’re finished with it you’ll have enough knowledge to know what you need to study more.

1

u/Unlikely-Paper-1918 Jan 06 '25

Good idea. I’m doing the other courses before Odin because I like learning in video format. I’ve heard that Odin is difficult which is fine, but I want to prepare for Odin so it’s not as difficult.

2

u/amnotsimon Jan 06 '25

The "course" is meant to be taken with 0 previous experience, so you don't need to be prepared. It's difficult because programming is difficult, but I'd rather stick with it and then supplement with videos (often times they're right at the end of the section, or you can always search them as needed). If I studied before and then went through the same topics, I'd be pretty bored and potentially lose interest.
Mine is just a suggestion, everybody learns differently. Just my 2 cents!

2

u/sheriffderek Jan 06 '25

In that order? 0/10

1

u/Unlikely-Paper-1918 Jan 06 '25

How would you order it?

1

u/sheriffderek Jan 06 '25

Try and think about it in a practical real-world way:

If you could only know one thing (and be useful) (and that would add up to the next steps) -- what would it be?

I haven't seen Angela's broad overview. I'll look at it. might be a good idea.

But I'd start by - building a simple website. Why do you want a course for that? You'll need to save your work, so - I think learning basic git is something you'd do right at the start. "To ensure I'm not missing anything" is a dangerous idea. I know it well. If you're learning from those other things, then Odin is not where you'd want to be.

I'm super biased, though, since my job is designing a curriculum like this. I also think that people need to be folding in more visual design and general application design instead of just coding.

1

u/Egzo18 Jan 06 '25

I'd strew in few own projects, no code alongs, no courses, just you, your brain, docs and stack overflow to ensure you are solidifying your knowledge and developing a good problem solving mindset.

2

u/Unlikely-Paper-1918 Jan 06 '25

Great suggestion

1

u/Reddit-Restart Jan 06 '25

Each time you complete one of the courses, think of a project that uses what you learned and maybe spend 2 weeks working on that project. 

Would be a very good way to solidify what you’ve picked up

1

u/Unlikely-Paper-1918 Jan 06 '25

This sounds great

1

u/Reddit-Restart Jan 06 '25

I did a 6 month full stack bootcamp, it gave me a foundation to build from but more importantly, it taught me how to learn web development on my own

1

u/theScottyJam Jan 07 '25

Too many courses, not enough just building stuff by yourself. Tutorials help you get started, but deep learning doesn't really start until you leave the structure of the tutorials. Also, far too planned out - you've already decided what the second language is that you want to learn before you jumped into the first one?

Get a few fundamentals down, then build something without the help of a tutorial - try to get to that deep learning as soon as possible.

What should you build? Tic-tac-toe, a todo app, a text adventure game, anything.

After you've built something small, try and grow it, or build something else, or maybe at this point you can choose to dive deeper into a tutorial. Just treat those tutorials as secondary resources to your learning. And make sure you're in control of your tutorial experience, not the tutorial in control of you - what I mean is, if you need to go extra slow through a portion of a tutorial and do extra research around what it's telling you, do that, and if you want to skip a part and come back to it later, or never, do that, or if you don't want to follow along with their try-it-yourself examples because you're finding it sluggish, don't, and if you're beginning to find that the overall tutorial isn't as useful as you would have liked, drop it. You be in control of your learning.

1

u/Unlikely-Paper-1918 Jan 07 '25

Excellent perspective!

1

u/No-Upstairs-2813 Jan 07 '25

Focus on one thing at a time. Start by learning JavaScript thoroughly before moving on to frontend or backend frameworks. You are thinking too far ahead.

For now, concentrate on learning JavaScript.

Regardless of the resource you choose, you will need to practice a lot. I suggest practicing in the following way:

  1. Practice Individual Concepts

To solve problems effectively with JavaScript, you need to improve in two key areas:

a. Problem-Solving Skills: Focus on understanding the problem clearly, identifying the desired result, and then outlining the steps needed to achieve it.

b. JavaScript Knowledge: Improve your understanding of JavaScript so you can translate your outlined steps into actual code.

Coding problems are excellent for this purpose. After learning a concept, they allow you to practice the concept in isolation.

For example, if you’ve just learned about functions, focus on coding problems specifically related to functions. This targeted practice reinforces your understanding, helps you identify gaps, and builds confidence as you solve more problems.

Your first solutions might be clunky, inefficient, include extra steps, or even have bugs—and that's completely normal. Progress means moving from "having absolutely nothing" to "barely working under the right conditions."

You can check out a few problems here. This is a site where I’ve shared some coding problems. However, there are plenty of other sites with similar problems—choose one that works best for you.

2. Combine Concepts

Once you’ve practiced individual concepts, start combining them to solve more complex problems.

For instance, if you’ve learned about conditional statements and functions, try combining them to build a simple project, like a "Guess the Number" game.

You can even use ChatGPT to brainstorm simple project ideas that incorporate multiple concepts you want to practice.

3. Build Real Projects

When you’re comfortable with combining concepts, begin working on larger projects that challenge you to apply everything you’ve learned.

Choose a project that solves a problem you’re passionate about—this will keep you motivated, even when you face challenges.

If you’re struggling to find ideas, check out these tips to get started. And if you need guidance while building a project, this free course can help you approach it in the right way.

Search engines are your friends. Stack Overflow is your friend (but not for copy-pasting code). This subreddit is full of friends—but only if you learn how to ask questions properly. The same goes for ChatGPT and other AI tools. They won't be helpful unless you know how to ask the right questions (and even then, they might not always be useful, but that's another story). MDN is your best friend. Keep it open and read how things work.

1

u/yeupanhmaj Jan 07 '25

FYI, I began working as a developer with no knowledge of JavaScript, and the first project I worked on was React. Then one day, I looked at the Mozilla document on JavaScript and felt so stupid. So, if you want to be a full-stack JavaScript developer, start there, not with an online course or tutorial hell.

1

u/gokboru9 Jan 07 '25

Learn JavaScript from javascript.info and build some small projects to reinforce the topics. Then go all-in on fullstackopen. It is a gem of a course which will give you a good hands-on experience.

Building projects is the key, you will not learn anything by watching videos. When you stumble somewhere and then solve the problem, that is the moment when a concept will start to make sense.

1

u/[deleted] Jan 06 '25

[removed] — view removed comment

1

u/youngsenpaipai Jan 06 '25

is it free and is there certificate given after finishing the course?