I really like how this channel doesn't retread ground - it's always something new that even larger channels tend to skim over even with how roadblocks like these are super common.
I was stuck in tutorial hell when I started learning programming through TH-cam tutorials labelled as "from absolute beginner to advanced" or something like that. The problem with these tutorials was that the uploader taught everything from the declaring variables to some Object-Oriented programming but never specified that the whole point of programming was that you have a problem and need to figure out a solution for said problem, nor did he provide any exercises that were meant to challenge the viewer's understanding of the subject and then show a solution to help them figure stuff out, neither did he mention that in order to improve your programming and problem-solving skills you need to do lots of practice. Also these tutorials more often that not don't point you to where you need to go next in order to expand your knowledge. My current method of learning new stuff is, as you pointed out in the video, the official documentation. Also books, lots and lots of books. Their scope isn't exactly the same as the documentation but I can't stress enough how helpful they've been to me.
Tutorial hell is exactly how I tried to learn UE4 blueprints, as soon as I went off video I struggled real hard and kept returning to tutorials out of desperation. Appreciate you sharing this perspective!
I was about to just open the video and scrub through to see what it was about, but that intro was enough to convince me I needed to see the whole thing😂😂😂
I wholeheartedly get behind this. I see so many devlogs where the dev googles everything they're making and I start wondering if they even made it. They just glued everything together in a hot mess. I also find a lot of devs creating their own tutorials for things they literally just watched a tutorial for. Whilst I understand making a video about it can help you understand it better, surely redirecting people to that original tutorial is better and you can build something on top of that. That being said tutorials are excellent ways to start off. I began with game maker tutorials but after the tutorials I tried to implement my own features with that code base. X years later (Unfortunately that is a roman numeral :'( ) I have learnt to work out my problems and rarely consult tutorials in these fields.
I like this video because I am stuck for a few years in this cycle. I use software, watch tutorial, learn more, but don't deep dive into anything. But then I think "no, I am developing the holistic map of everything I am learning in my mind, which should make everything fit together more naturaslly. I am building a little knowledge in all areas, which will combine like Voltron".
My whole thing is, my game ideas are just inspired by games i played growing up (mostly linear jrpgs), so i dont want to experiment with physics mechanics and whatnot. i just want to frankenstein existing game mechanics that already exist from other games and put my own twist on it, than figure out how to do it by myself when its already been done before by a lot of people (dialogue boxes, save points, etc). Ive managed to figure out some things on my own. and im more of a visual learner, so i perfer to be handed a fish, so i can dissect and understand it xD documentation confuses me without visual examples. btw im using a visual scripting asset too so lol
i love these kinds of videos. i also add try to implememt one or two additional features in the project while following the tutorial for that project. This helps alot in learning, When stuck stackoverflow is your friend. But don't use it until you tried your best to solve it yourself.
Yeah I figured out that everytime i learn a skill I feel lost because there is so much. What I learned to do was to focus on one task at a time and not worry about how long it takes to do it. I spent 12 hours just trying to have my object move in the same direction of my mouse's movement at a constant speed. I gained a lot of experience through it. I started writing code much faster and my understanding of code jumped a lot. I used a bunch of different tools to figure out how to get it to do what I wanted so I gained a lot of experience with multiple tools and a lot of understanding of when to use those tools and when not to. focusing on one task at a time really made me feel much less lost.
Really great video. I have noticed myself fall into this trap many times over the years, especially when watching video tutorials. It's easy to just zone out and copy the code line for line. One thing I started doing to combat this (usually works better with written code tutorials on blogs rather than videos) is to stop after a step in the tutorial, and try to predict what the next step is and implement it myself. Or often in coding tutorials there will be a written description of the next step before they show the code, so I try write the code based on the description of the next step before looking at the code they've written for it. These don't work for all tutorials and rely on some knowledge so not the best for beginner tutorials, but they help keep me engaged and actually process the tutorial content.
I must say that you are very underated for the content you are putting out, both in production quality and otherwise. Keep up the good work. Found you in bandsmens server btw hahaha
Hey there, great vid! Besides the good content, I wanted to compliment you on the style of the video and the editing. Your style and delivery is something that I'm trying to achieve myself (slowly but, hopefully, surely) :)
I feel that the problem is too is that.. people just go straight into it without any programming knowledge, including me. I basically never used a switch case because... I never actually bothered learning what a switch case and used nest if else statements ( oh God, the memory allocation storage.) Also when you're working on a low level framework like Raylib or XNA like I am.... with documentation not being all that great.... it REALLY starts to irk the hell out of you when you are trying to start and don't know where to even begin. Although I do agree that by looking at the documentation and with some help from forums, I do get way farther on my own instead of relying on 3 hour long tutorials.
I dont know why, even your longer videos are so interesting that I don't get bored...! Just came here after your GameDev maths video (20min long) & it's damn addictive 🌟
That's actually so related to many people. Like a plenty of them copies tutrorials step by step, without completely understanding what thay are doing. I try to create "tutorials" (about programming different stuff) wehere I don't show the code or say what to type. I explain things in depth like the math part there
General Kenobi (If you get the reference) You content is awesome! Saw a Reddit post for your video of free tools for indie dev and I knew this channel is gold. Keep up the great work!
I like your saying about fish but I like this one better... Give a man a fire and he's warm for a day, but set a man on fire and he's warm for the rest of his life.
Ok, here's a good praticse on how to follow a tutorial: watch the tutorial, but do not code along (i will focus on code because i'm a programmer, but with a bit of tweaking, this technique can be applied to pretty much everything), instead watch it until the end, then close the tutorial and try to code it for yourself (that way you're basically forced to try to learn what's going on in it) and if you get stuck, close your code-writing app and repeat the process from the start, until you manage to make what you want to achive (it's kinda like if you were at shool learning something). Also, form my feeling, most of the coding tutorial out there are "made to be copy pasted" and don't explain in-depth enough what's going on or why is that happening in a code: That's why i think making a good tutorial is super hard imo. A good example of a tutorial done well imo is the tutorial series on how to make a game engine in Java/OpenGL of ThinMatrix (go follow the guy if don't know it already, he's awersome): First he explain the basics of how the logic of what he want's to do works, then he codes it along, still reminding the logic while coding it, and finally he goes to show the most common flaws and errors and how to fix them. Plus, despite the topic being a complex one, his tutorials they never feel too complex to understand, even if you're a complete noob on the topic. And yes, documentation is king when it comes to actually learn how to do something, especially if you're trying to do that on your own. It can feel a bit overwelming at first, but try to stick to it: it will make you a better programmer, trust me guys!!! Documentatiin first, tutorials later (if still needed, that is 😉)
What i do when watching a tutorial is i look at the script and try to understand it then change values around a lot, at the end of the first tutorial i saw for godot my game looked nothing like the tutorial XD I didn’t even use the supplied 3d models, i made my own in blender despite never using it before
How do you not have a million subscribers. I was in this exact place a few years ago! This was really high quality and real! I am subbed because if your content is as good as this you more that deserve it!
My experience with learning programming has been a whole mess for the 5 years I've been doing it, and I'm bored so I'm going to recount the entire story here. It started in a generic high school cs class, where we were being taught python, but the teacher sent us to the wrong site and we were learning javascript for about 2 weeks. I as somebody who cared about the subject realised this and discovered w3, so when we started the right thing, I knew what was going on, and ended up spending most lessons solving the same problems 20 times in a row because I understood what "print()" does. Eventually I moved on to my own programming, and as a beginner I needed tutorials, and I got nowhere because tutorials are always framed towards a specific variant of a problem, and never teach how to apply their lesson to other scenarios. Until eventually I discovered documentation (and stack overflow), which is how I'm somehow in the same cs class, but able to answer the generic algorithm problems in ways that nobody should ever answer them
There are lots of places! Like I said, tutorials aren't strictly bad, we just need to approach them in the right way. Really try to understand WHY the tutorial teacher is writing each line of code, instead of just copying it without thinking. Then, before moving onto the next tutorial or blog, check you understand exactly what the code is doing by intentionally changing aspects of it with a specific outcome in mind - if it breaks, figure out why until you understand how it works. Project drifter will be back in a couple of weeks, just need some more dev time to work on it for a bit!
Really nice and well explained, well made video, i subbed :D Thankfully i dont fall in to this category anymore hehe but i id did when i started with unity, several years back i remember :D, and also good tutorials maby have some funn aspect/twist to them but also properly explane stuff and maby show How What why the code is what it is how etc, in the early days it also helped to mdofying variabels etc to see what happenedto also see visual what happened like changing speed of a player object etc :D
I don't really agree with the analogy, or most of the video for that matter. Talking from my own experience, I've never had this issue. I think tutorials do indeed teach you how to fish, and code snippets without any further explenation is closer to "handing someone a fish". Looking at Brackeys and the official Unity tutorials, I never had any problems understanding the code and knowing how to manipulate it to my liking. Great video, but a lot of it seems like a stretch. The advice at the end is really useful though, regardless of the first part, so this is still a very solid video, nice job
Thanks! I think it's a problem that will mostly be experienced by newer developers, and can be easy to overlook when we have years of experience under our belts. Of course, it's a feeling some people might never experience at all, so fair enough if you've never had this problem aha
Ah I'm so glad you are finding these video's helpful! I'm always aiming to help other people with each video I release, so it's really nice to comments like this!
I don't like tutorials for beginners. It's like starting a game and just skipping towards the last boss without really playing the game. Coding and design is not the only part of game development there is art, music, ect
Right! Documentation is hard to understand, but once you know the basics you better spend more and more time studying documentation, rather than watching countless tutorials
I just stuck with tutorial on opengl by the cherno, instead of using glm library I tried to make my own library but then stuck trying to make it as fast as possible and learn new stuff about quaternions matrices Taylor's and other's series polynemes, I am just lazy and dont get enough sleep that's the problem
Ok first of all there is no tutorial for art now when its come to coding I dont even watch the tutorial , Copy - > paste and DONE!! 👍👍👍👍👍 what to do now
Interesting video! but from my experience, tutorials made me learns, by coping and following the tutorials I learned with time, so I was better to know what to do in some context etc. But yeah really cool, I like the name!
Yah basically gamedev is not biology where there's a 1-1 solution you memorize. Tutorials are fine as long as u have a good programmer-based learning thing going. i suck at words.
I really like how this channel doesn't retread ground - it's always something new that even larger channels tend to skim over even with how roadblocks like these are super common.
I was stuck in tutorial hell when I started learning programming through TH-cam tutorials labelled as "from absolute beginner to advanced" or something like that. The problem with these tutorials was that the uploader taught everything from the declaring variables to some Object-Oriented programming but never specified that the whole point of programming was that you have a problem and need to figure out a solution for said problem, nor did he provide any exercises that were meant to challenge the viewer's understanding of the subject and then show a solution to help them figure stuff out, neither did he mention that in order to improve your programming and problem-solving skills you need to do lots of practice.
Also these tutorials more often that not don't point you to where you need to go next in order to expand your knowledge.
My current method of learning new stuff is, as you pointed out in the video, the official documentation. Also books, lots and lots of books. Their scope isn't exactly the same as the documentation but I can't stress enough how helpful they've been to me.
Tutorial hell is exactly how I tried to learn UE4 blueprints, as soon as I went off video I struggled real hard and kept returning to tutorials out of desperation. Appreciate you sharing this perspective!
I was about to just open the video and scrub through to see what it was about, but that intro was enough to convince me I needed to see the whole thing😂😂😂
I found you in jabrils discord, glad I did. I loved the content, keep up the great work
You need advertising. This is way too much juicy, amazing content not being seen by other devs! #underratedisanunderstatement
I wholeheartedly get behind this. I see so many devlogs where the dev googles everything they're making and I start wondering if they even made it. They just glued everything together in a hot mess.
I also find a lot of devs creating their own tutorials for things they literally just watched a tutorial for. Whilst I understand making a video about it can help you understand it better, surely redirecting people to that original tutorial is better and you can build something on top of that.
That being said tutorials are excellent ways to start off. I began with game maker tutorials but after the tutorials I tried to implement my own features with that code base. X years later (Unfortunately that is a roman numeral :'( ) I have learnt to work out my problems and rarely consult tutorials in these fields.
I like this video because I am stuck for a few years in this cycle. I use software, watch tutorial, learn more, but don't deep dive into anything. But then I think "no, I am developing the holistic map of everything I am learning in my mind, which should make everything fit together more naturaslly. I am building a little knowledge in all areas, which will combine like Voltron".
My whole thing is, my game ideas are just inspired by games i played growing up (mostly linear jrpgs), so i dont want to experiment with physics mechanics and whatnot. i just want to frankenstein existing game mechanics that already exist from other games and put my own twist on it, than figure out how to do it by myself when its already been done before by a lot of people (dialogue boxes, save points, etc). Ive managed to figure out some things on my own.
and im more of a visual learner, so i perfer to be handed a fish, so i can dissect and understand it xD documentation confuses me without visual examples. btw im using a visual scripting asset too so lol
I hit f5 it refreshed my page
i love these kinds of videos.
i also add try to implememt one or two additional features in the project while following the tutorial for that project. This helps alot in learning, When stuck stackoverflow is your friend.
But don't use it until you tried your best to solve it yourself.
When I first started, I was really stuck there, but when I stopped using tutorials, it really let me be creative and make new stuff! Great video! 👍😀
Yeah I figured out that everytime i learn a skill I feel lost because there is so much. What I learned to do was to focus on one task at a time and not worry about how long it takes to do it. I spent 12 hours just trying to have my object move in the same direction of my mouse's movement at a constant speed. I gained a lot of experience through it. I started writing code much faster and my understanding of code jumped a lot. I used a bunch of different tools to figure out how to get it to do what I wanted so I gained a lot of experience with multiple tools and a lot of understanding of when to use those tools and when not to. focusing on one task at a time really made me feel much less lost.
Really great video. I have noticed myself fall into this trap many times over the years, especially when watching video tutorials. It's easy to just zone out and copy the code line for line. One thing I started doing to combat this (usually works better with written code tutorials on blogs rather than videos) is to stop after a step in the tutorial, and try to predict what the next step is and implement it myself. Or often in coding tutorials there will be a written description of the next step before they show the code, so I try write the code based on the description of the next step before looking at the code they've written for it. These don't work for all tutorials and rely on some knowledge so not the best for beginner tutorials, but they help keep me engaged and actually process the tutorial content.
I must say that you are very underated for the content you are putting out, both in production quality and otherwise. Keep up the good work. Found you in bandsmens server btw hahaha
Hey there, great vid! Besides the good content, I wanted to compliment you on the style of the video and the editing. Your style and delivery is something that I'm trying to achieve myself (slowly but, hopefully, surely) :)
I feel that the problem is too is that.. people just go straight into it without any programming knowledge, including me. I basically never used a switch case because... I never actually bothered learning what a switch case and used nest if else statements ( oh God, the memory allocation storage.) Also when you're working on a low level framework like Raylib or XNA like I am.... with documentation not being all that great.... it REALLY starts to irk the hell out of you when you are trying to start and don't know where to even begin. Although I do agree that by looking at the documentation and with some help from forums, I do get way farther on my own instead of relying on 3 hour long tutorials.
I dont know why, even your longer videos are so interesting that I don't get bored...! Just came here after your GameDev maths video (20min long) & it's damn addictive 🌟
That's actually so related to many people. Like a plenty of them copies tutrorials step by step, without completely understanding what thay are doing. I try to create "tutorials" (about programming different stuff) wehere I don't show the code or say what to type. I explain things in depth like the math part there
General Kenobi (If you get the reference) You content is awesome! Saw a Reddit post for your video of free tools for indie dev and I knew this channel is gold. Keep up the great work!
Dude, great video! I feel like ALL new devs absolutely need to watch this before jumping into game dev!
You deserve more subscribers man!
The message and editing is on point! Everyone needs to watch this.
Congrats on 400 madbook
This video was so insightful. Thank you!!
I feel like you just saved my life.
I like your saying about fish but I like this one better...
Give a man a fire and he's warm for a day, but set a man on fire and he's warm for the rest of his life.
Ok, here's a good praticse on how to follow a tutorial: watch the tutorial, but do not code along (i will focus on code because i'm a programmer, but with a bit of tweaking, this technique can be applied to pretty much everything), instead watch it until the end, then close the tutorial and try to code it for yourself (that way you're basically forced to try to learn what's going on in it) and if you get stuck, close your code-writing app and repeat the process from the start, until you manage to make what you want to achive (it's kinda like if you were at shool learning something).
Also, form my feeling, most of the coding tutorial out there are "made to be copy pasted" and don't explain in-depth enough what's going on or why is that happening in a code: That's why i think making a good tutorial is super hard imo.
A good example of a tutorial done well imo is the tutorial series on how to make a game engine in Java/OpenGL of ThinMatrix (go follow the guy if don't know it already, he's awersome): First he explain the basics of how the logic of what he want's to do works, then he codes it along, still reminding the logic while coding it, and finally he goes to show the most common flaws and errors and how to fix them. Plus, despite the topic being a complex one, his tutorials they never feel too complex to understand, even if you're a complete noob on the topic.
And yes, documentation is king when it comes to actually learn how to do something, especially if you're trying to do that on your own. It can feel a bit overwelming at first, but try to stick to it: it will make you a better programmer, trust me guys!!! Documentatiin first, tutorials later (if still needed, that is 😉)
Aww, shoot. I wrote too much xD
programmers googling everything on stackoverflow be like
What i do when watching a tutorial is i look at the script and try to understand it then change values around a lot, at the end of the first tutorial i saw for godot my game looked nothing like the tutorial XD
I didn’t even use the supplied 3d models, i made my own in blender despite never using it before
How do you not have a million subscribers. I was in this exact place a few years ago! This was really high quality and real! I am subbed because if your content is as good as this you more that deserve it!
Exactly me
My experience with learning programming has been a whole mess for the 5 years I've been doing it, and I'm bored so I'm going to recount the entire story here.
It started in a generic high school cs class, where we were being taught python, but the teacher sent us to the wrong site and we were learning javascript for about 2 weeks. I as somebody who cared about the subject realised this and discovered w3, so when we started the right thing, I knew what was going on, and ended up spending most lessons solving the same problems 20 times in a row because I understood what "print()" does. Eventually I moved on to my own programming, and as a beginner I needed tutorials, and I got nowhere because tutorials are always framed towards a specific variant of a problem, and never teach how to apply their lesson to other scenarios. Until eventually I discovered documentation (and stack overflow), which is how I'm somehow in the same cs class, but able to answer the generic algorithm problems in ways that nobody should ever answer them
Either you're looking for someone to solve your problem for you or you're learning to improve. Hope folks choose the right path 🙂
dayum never thought of it this way lol i finally got out of it and almost got into it again when making music for the game
Great video my dude!
Do you know where to learn the basics of code, also whens the next project drifter devlog
There are lots of places! Like I said, tutorials aren't strictly bad, we just need to approach them in the right way. Really try to understand WHY the tutorial teacher is writing each line of code, instead of just copying it without thinking. Then, before moving onto the next tutorial or blog, check you understand exactly what the code is doing by intentionally changing aspects of it with a specific outcome in mind - if it breaks, figure out why until you understand how it works.
Project drifter will be back in a couple of weeks, just need some more dev time to work on it for a bit!
nice video i liked the analogy you used
Its all about to that stackoverflow life baby
ctrl+c, ctrl+v babyyyyy
"Tutorial hell" is short for "not being able to think by yourself"
Tutorial hell: Like development hell but JUST FOR YOU! A+ vid!
You should think about doing a series similar to Jonas's "I play your indie games" where you could give us feedback when we have no friends :D
Really nice and well explained, well made video, i subbed :D
Thankfully i dont fall in to this category anymore hehe but i id did when i started with unity, several years back i remember :D, and also good tutorials maby have some funn aspect/twist to them but also properly explane stuff and maby show How What why the code is what it is how etc, in the early days it also helped to mdofying variabels etc to see what happenedto also see visual what happened like changing speed of a player object etc :D
I don't really agree with the analogy, or most of the video for that matter. Talking from my own experience, I've never had this issue. I think tutorials do indeed teach you how to fish, and code snippets without any further explenation is closer to "handing someone a fish". Looking at Brackeys and the official Unity tutorials, I never had any problems understanding the code and knowing how to manipulate it to my liking. Great video, but a lot of it seems like a stretch. The advice at the end is really useful though, regardless of the first part, so this is still a very solid video, nice job
Thanks! I think it's a problem that will mostly be experienced by newer developers, and can be easy to overlook when we have years of experience under our belts.
Of course, it's a feeling some people might never experience at all, so fair enough if you've never had this problem aha
@@Madbook Yea, you make a good point!! You know what you're talking about
I FEEL GRATEFUL, THANKS
I recently starting learning unity and game Dev from udemy and this information is very helpful. Thanks a lot. BTW recently means just 2 days. 😁😂
Ah I'm so glad you are finding these video's helpful! I'm always aiming to help other people with each video I release, so it's really nice to comments like this!
I don't like tutorials for beginners. It's like starting a game and just skipping towards the last boss without really playing the game. Coding and design is not the only part of game development there is art, music, ect
Right! Documentation is hard to understand, but once you know the basics you better spend more and more time studying documentation, rather than watching countless tutorials
I just stuck with tutorial on opengl by the cherno, instead of using glm library I tried to make my own library but then stuck trying to make it as fast as possible and learn new stuff about quaternions matrices Taylor's and other's series polynemes, I am just lazy and dont get enough sleep that's the problem
Me using unity ml-agents: Where docs? (The docs are outdated lmao)
Great video
Ok first of all there is no tutorial for art now when its come to coding I dont even watch the tutorial ,
Copy - > paste and DONE!! 👍👍👍👍👍 what to do now
Interesting video!
but from my experience, tutorials made me learns, by coping and following the tutorials I learned with time, so I was better to know what to do in some context etc.
But yeah really cool, I like the name!
Yah basically gamedev is not biology where there's a 1-1 solution you memorize.
Tutorials are fine as long as u have a good programmer-based learning thing going. i suck at words.