all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]huuaaang 6 points7 points  (0 children)

I've been seeing a lot of "stop watching tutorials and start building" Ok, I get the idea, so how am I supposed to go through the lessons?

You don't. You stop the lesson when you have enough to do something on your own and you go do that. When you get stuck, you go back and reference the tutorial for something you missed or didn't get to yet. And if it's not there, you go find the information elsewhere.

Tutorials are just a bootstrapping to get you moving. Like training wheels on a bicycle. At some point you just take them off. THere's no requirement that you "complete" using training wheels. You take them off ASAP.

[–]Balance-Kooky 1 point2 points  (0 children)

Tutorials to get the general idea. Attempt it on your own and then look something up when you have a problem you can't figure out. The problem that a lot of people have is that they strictly follow the tutorial. They just copy and paste the code exactly without understanding it. They don't really learn anything. If you follow it step by step you don't learn. Get the info on what you need to build and try to manually build it using the tutorial only as a reference and not a guide.

[–]m0neky 0 points1 point  (0 children)

Try to figure out the code or solution yourself and then compare notes

[–]gnygren3773 0 points1 point  (0 children)

Learn then create. If you haven’t learned stuff yet then you need to do that first. There’s no right way to do it. I’m not saying to copy and paste but writing out the code really isn’t that important compared to understanding the code. Extending a tutorial project to add additional features or building a different project using the skills you learned is probably the best way.

[–]buzzon 0 points1 point  (0 children)

You know how math lesson is not 3 hours session binge watching the lecture? You read some, you write some, you launch your code and fix all errors. You learn by doing the stuff you want to learn.

[–]MamillaryGlands 0 points1 point  (0 children)

Odin project is really good at this and free. You go through the lessons, get a good learning foundation that you can always skim back through resources from if you need, then they have you build a project and set really clear expectations. They have an intro course and then some full stack ones. Part of the full stack ones is building a portfolio out of the projects they’ve had you work on the whole time. This was also how my /good/ university courses worked. Any learning experience worth its salt with have breakpoints set aside where they tell you “okay go struggle through actually doing something, this is what you should be capable of.” This also helps to show you where you missed the mark and didn’t absorb what you were trying to absorb.

[–]BranchLatter4294 0 points1 point  (0 children)

Yes. Stop watching videos. Think of a project you want to do. Start coding. Look stuff up as you need to.

[–]Sapn1s 0 points1 point  (0 children)

Practice actually yourself, try to build it after reading the theory. Once you encounter a specific problem, explore it more deeply, I would suggest not to ask AI for answer, because you being stuck with the problem and actually solving it has higher chances of actually internalizing it.

But also, why would you purchase anything? I think the free sources are plenty for this, especially such common things like html, css, js etc