To try everything Brilliant has to offer—free—for a full 30 days, visit https://brilliant.org/TheCodingSloth . You’ll also get 20% off an annual premium subscription.

Instructions unclear, am now stuck watching a tutorial on getting out of tutorial heck

Watching a tutorial on how to escape tutorial hell is peak tutorial experience

I have chatgpt hell

A think you didn't mentioned: The project you choose shouldn't be something you're 100% confident that you KNOW how to make. Get used to learning as you go.

I'm a trash programming noob but I've never been stuck in tutorial hell. I think one way to think about "how to use tutorials" is not a "how to make a hangman game" tutorial but to start making it, get stuck on a specific thing, then look at e.g. "how to use multiple arguments in a function" tutorial, or a "how to splice an array", or whatever. At least that's how I learned. Still trash though. But I was able to make a simple garden tracker with that method.

I figured out why I like this channel! This channel's editing is reminiscent of YouTube videos I watch for fun, while also talking about subjects I like to learn about!

00:02 Tutorial hell is a state of overreliance on tutorials while lacking confidence and skills. 01:07 Being stuck in tutorial hell limits your growth as a programmer. 02:08 Use tutorials more effectively 03:13 Brilliant is effective for problem-solving and not memorization 04:14 Start small and set clear goals 05:12 Break down coding tasks into small steps 06:07 Use tutorials as reference, not as dependency. 07:09 Using tutorials for specific concepts is fine, but avoid complete dependency.

good video, wish i would have seen this before watching the 4h bro code video on C for an exam i have tomorrow

My greatest tip to anyone reading is to start a tutorial and instead of blindly reading the info and copy pasting the code, follow the tutorial using another language and/or library and/or adding more stuff on top. This will throw you into many errors that no manager or tutorial could ever teach you about preemptively and only through doing actual engineering will you be able to finish a tutorial while doing extra stuff. If you can't do that, then simply pivot to a more easier tutorial to try and as your actual important software engineering skills are being developed subconsciously, eventually you'll recognize you can solve whatever got you stuck last time in the hard tutorial. Another tip is to not copy paste code, but to write it. Just like rote memorization, this helps in many non obvious ways months down the line. It also helps cement boilerplate and programming code patterns which you can more easily remember and then use later down the line.

Tutorials only teach you the right way but it doesn't teach you the 10,000 times you need to fail

One addition to your video (which I agree with): While going through the tutorial to learn the concept, throw it in a git repository. Commit it in the state at whatever point you are in the tutorial. Start experimenting and trying out random stuff to see how it changes the results of your code. Use that to understand what everything does. Once you're done, you can revert your wacky experiment and continue with the tutorial. This gives you a chance to think and learn in a way blindly copying a tutorial never will.

Bro code ,mentioned😮

To me getting out of tutorial hell is truly a matter of not interfering too much with the critical thinking in learning. We use calendars and to-do lists so we don't have to hold and process information in our brain. If you treat tutorials like a calendar or to-do list then you're not giving your self a chance to think critically about the problem you're solving. I suggest writing down all the questions you want to look up in a list that you can search AFTER trying to think for yourself. For me I usually give myself 30 minutes of being stuck before I start looking things up.

hey dad when you coming back home

Another way of escaping tutorial hell I can recommend (though I'm sure it won't work for everyone, probably only the minority) is to actually think and analyze things you're watching. At some point I just started thinking "hey this tutorial sucks, I would've done it differently, would have been much easier/shorter" or "I didn't know you can do it like this, that's cool". It really helped me get some patterns and concepts in my head. Didn't write a single line of code from any tutorial (though I did start making a project at some point, that definitely helped as well. But it wasn't everything, I was already primed to analyse code and do things myself then). So if your brain works this way, try it! Doesn't beat actually making things, but it still teaches you way more than just copying code in my opinion. Though you need to watch a variety of topics by a variety of different people, to actually find things you like and dislike, since one person will likely just do things the same.

no way a tutorial on how to escape tutorial hell, this could never possibly go wrong!

5:40 "You will your google search ready😂... Got me rolling on the floor 😅

I pretty much rely on Chat GPT for building my Incremental game in Roblox Studio. I try to work on the components of my game and gradually build up my foundation over time. Trying to make the building process flexible, adaptable, and less busy is the hardest part of Game Development. It requires a lot of foresight; you have to imagine all the possible obstacles before you or else you'll crash and burn. If you are in Chat GPT Hell, please do me a favor and have your focus be narrow to complete specific goals of your project. Coding Sloth your content is pretty good, keep going my animal friend!

I suffer from tutorial heaven.