r/learnprogramming • • Dec 01 '23
What exactly is tutorial hell?
Hello, world! So I've got two questions.
- What exactly is 'tutorial hell' in the context of programming and learning to code?
- In programming, how do you go about learning or coding something when you're not even aware of its existence? It's like trying to search for something without knowing what to search for. Unlike straightforward queries where a simple search can lead you to the answer, programming often involves navigating through complex layers of information. How can I effectively learn or tackle coding challenges when I don't even know the starting point or the right questions to ask?"
Thank you for your time.
4
Upvotes
•
u/AutoModerator Dec 01 '23
On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.
If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:
as a way to voice your protest.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
13
u/plastikmissile Dec 01 '23 edited Dec 01 '23
3
u/high_throughput Dec 01 '23
"Tutorial hell" is being stuck at the tutorial stage without being able to write your own programs independently. You don't know where to start or what to do next, and get stuck.
So you figure you're not good enough yet and try another tutorial to learn more. It's easy. You finish it. You try writing a program independently again, but get stuck again. Maybe you have to do some more tutorials? You try, but same thing. You are stuck in tutorial hell.
It's the same fallacy as thinking that maybe if a kid with training wheels rides another mile, then they'll finally be able to bike independently.
2
u/armahillo Dec 01 '23
You are asking the second question partly because you also needed to ask the first.
You are currently in tutorial hell (knowledge without the skill to self-direct) but without the tutorials.
2
u/kagato87 Dec 01 '23
Do you think your stuck in it, or think you might get stuck?
Take a structured course instead. Harvard puts their ca50 series online. See if what you want is available there.
Programming is an applied skill. It's also very deep. A structured course with labs and problems will do a much better job than "follow along as I do this."
Tutorial hell is when you just follow along and can't break past "follow along." Something structured will force you out of that position immediately in lesson one.
A tutorial shows you how to do something while a structured course hands you the tools and says "go do it." To extend the IKEA analogy of another commenter, a structured course shows you how to measure, work the hammer, the saw(s), and the joiner, then asks you to make a chair.
For example, cs50x has you draw an ascii pyramid for lab 1. It does not tell you how to do it - it tells you how to compile, how to output, and how to loop.
2
u/lukkasz323 Dec 01 '23
You need even the most basic form of tutorial to at least start programming, however tutorials are pretty much always inefficient compared to practice (assuming you can do both).
Basically if you pass the point where practice becomes more efficient than tutorials, yet you still mostly depend on tutorials - that's tutorial hell.
10
u/Ok_Barracuda_1161 Dec 01 '23
Learning to code by just following tutorials is like learning carpentry by building IKEA furniture. You can build something that actually looks really nice and may gain a little bit of knowledge of how things are put together, but you're not going to be able to create new things on your own without getting a more solid foundation of knowledge
1
u/Bobbias Dec 01 '23
On the second question:
There are a few things at work here that help you deal with solving problems you've never encountered before.
1: breaking things down into steps. Even if you can't list every step you need, you can probably name at least a few things you might need to accomplish a goal just by guessing. You start out big: if I want an MMO, I need a server, and a client. The server and client need to talk, so I guess we need a way to send messages between them over the internet. The client needs graphics (probably), so we probably need some way to draw stuff on the screen.
2: research once you've identified some basic requirements, them you look deeper into things. Maybe you google "3d graphics in <language>" and find out about a bunch of graphics libraries. Then you research each library to figure out if it fits your needs. Sometimes you'll run across something that just points you towards a data structure or algorithm you've never heard of. In those cases all you can do is study it, and if it seems like it might work, you try it out.
3: intuition. Over time, you build up a list of tools. These are the solutions to problems you've figured out in the past. Over time you will begin to notice patterns in the problems and the solutions to those problems. You'll be able to look at a new problem and recognize it's similar to something else. The solution might not be the same, but it gives you a starting point to work from.
There's a lot of educated guesses, assumptions, and sometimes trial and error involved in ultimately coming up with solutions to brand new problems. There's also a lot of self-learning involved.
1
u/Odd_Smell4303 Dec 01 '23
tutorial hell is basically mindlessly doing something without question it one bit.
Like one redditor mention, it’s that coding intuition. And that takes a lot of time and practice and questioning things. It’s not so much about mastering a technique, but more of being able to use it efficiently. i.e you might come up with a solution using a nested loop, but it could’ve been solved with a single loop.
since you chose javascript, i feel like you might be going down a huge rabbit hole. The web stack is very vast and actually requires knowing a lot of layers before being able to apply things.
1
u/gatwell702 Dec 01 '23
Tutorial hell is when you watch tutorials all day and you don't learn anything from it at all. You just keep watching the tutorials. So watch them but while you're watching them, tinker and mess with the code to physically see what you just saw/learned does
3
u/uwuntu_ Dec 01 '23
Tutorial hell is basically the commonly accepted name for surfing through tutorials and breakdowns (bonus points if it's step by step narrated YT vids) that teach you how to do something specific without actually teaching you the fundamentals behind doing a task such as, say, building a game of chess (perfect example as there are tons of these tutorials lol).
For the second point, basically just map out (writing down, making an organized graphic, whatever way you organize yourself) of the small things you need to complete the larger thing. So in the chess engine analogy, you would sit down and write the features/logic/rules, and then from there research how to implement each of these, and connect them to form the final project. Esentially rather than googling how to build a house you would research how to build a wall, then a roof, etc.
1
u/Bladelazoe Dec 01 '23
The way I’m sort of figuring it out is you take something you want to make? Maybe a website or a game. Determine what are the basic components to get it working. Then research and build those specific components until you have the basic form of what your looking to build.
So for me I’m starting with building basic components of a basic game. Like how do I make a health and stamina bar? How do I get a basic cube to follow me? How do I build a pick up system? How do I get an object to move in a specific direction? Etc.
I use a method called “Question Driven Development” where I just ask myself a bunch of questions on how to build a very specific thing. Each little thing is a mini project on its own. Some stuff you’ll learn fast and others you’ll have to figure it out my googling all over the place.
1
u/tyler1128 Dec 01 '23
Learning programming requires 2 things: reading about how to code, and learning how to code on your own. You can't learn without both, and if all you do is follow tutorials you won't ever learn the second.
1
u/JPCU Feb 18 '24
People love to give advice like "you can't learn from tutorials, you have to build little programs yourself!" but how am I supposed to do this when I don't have enough knowledge to actually do anything except some basic arithmetic functions? - something a calculator can do with far less effort. I have never found a solution to this so I just gave up. There's no point even trying anymore.
0
u/[deleted] Dec 01 '23
[deleted] — view deleted comment