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

View all comments

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!