The problem is looking for specific tutorials, what you need is tutorials about how to use your engine, not how to make a game.

Using tutorials is not a bad thing for newbie developers; they can serve as a reference for how to solve a specific problem. If you use an external library for animation, calculating, or even an engine to complete your game, then using a tutorial can also save you time. It's always about how you use it in the progress; there's a fine line between reinventing the wheel and perceiving deep knowledge.

To discourage beginners to start their journey with simple tutorials is just horrible. By learning from examples you can grow and start to understand why the tutorial was made that way. Motivation is also a huge factor as many will be happy to see something work quickly and change it to their designs, and not have to search through comment sections of small games on a game jam. If you start by taking programming courses or doing only theoretical research instead of just starting to build, it might just kill of the motivation and many might stop just there...

Looking at the top game jam games I think is discouraging for a beginner because these games are usually made from veteran indies or professional coders that do games in their free time. Although there are some beginner game jams.

This video summed up: Here are the tools to create glass. Good luck! What? You want to be taught how? No, that will poison your progress in learning how to make glass. Have fun! What's that? You'll probably give up really quickly because you have no idea what you are doing? Oh, that's too bad. Well, I suggest checking out GlassDev and touch some different types of glass, that will for sure help you know how to create your own glass right? No? Well, I guess you can maybe watch someone online who will show you EXACTLY how to make glass you want to make step by step, and then find other videos that will help you add to your existing glass, thus making the ACTUAL glass you want. BUT ultimately that is a BAD idea because then your glass won't be sturdy enough if you just watch videos. So, really you should just stumble around in the dark for a LONG LONG time until you magically know what you are doing because remember....glass making is hard....

I never used feature specific tutorial as far as i can remember. If you are genuinely interested in game dev, you should explore the tools available to you (such as learning classes, objects, game engine insight), not what you CAN do. It will benefit you more to learn why and how popular features were made than to copy them. That in turn, will also will also allow you to innovate and make THE game you invisioned. Right now my challenge is actually finishing a game and then publisbing it :)

This is why I loved ThinMatrix's OpenGL tutorials since he doesn't show you how to make a game but the process and explanation of how and why you do things to build a game engine. This gave me a deeper understanding of how they work in general. I implemented my own systems on top of what I learned so it made me able to more easily use another engine and gave me a good understanding of syntax and logic. The only tutorials I watch are about a specific engine feature use.

The way out of that tutorial trap for me was learning the fundamentals of programming in order to understand enough to attempt to make my own mechanics unassisted. From there, keep trying and failing and eventually you'll know the pitfalls to avoid and good habits to get into early in your project

I'd argue that tutorials are a crucial step in learning game development without a technical computer science background. Documentation can be incredibly scary. As someone who started in tutorial purgatory but slowly learned how to problem solve for themselves, without tutorials I would not be where I am today, making a multiplayer game completely using documentation and my brain. Tutorials give you the tools you need but the only way to improve is to take what you learn and apply it.

What people have to remember is that something is better than nothing in most cases. If you're out of shape and want to get fit, anything that gets you moving more than you did before will get you results. Sure you should be aware of certain things as you improve such as proper form and having a routine that you follow, but remember that all of those things are there to support your primary goal. You can get MORE fit with improper form and a haphazard routine but you can't get MORE fit without working out at all. Injury prevents consistency, just as having no routine might. Only insecure people will laugh at another for mistakes. Now extrapolating that over to general game development, sitting there for days and weeks looking for the best way to do things is ultimately worse than starting. People say that adults have a harder time learning than children and while that might be true from a physiological standpoint, the bigger issue at hand is that as people get older, they become burdened by knowledge. Everything becomes a management of resources. "Is this going to be right for me? What's the fastest/best way to do XYZ? Can I make money out of this?" Kids on the other hand just do things because it's fun. If you truly enjoy something you will master it. It's going to be hard to shake habits and fears but trust the process. Whether it's random tutorials or reading documentation or taking formal lessons, all you have to do is start and stick with it. Completing a flawed tutorial is still more valuable than quitting a Masterclass.

I won't say Game Dev tutorials will poison your progress. This "tutorial hell" is Level 1 GameDev where surface level knowledge matters and everything seems like copy and paste, they are great at getting a person with 0 experience in game dev or a specific feature off the ground. At that point, the developer should know what he/she wants. If you feel discouraged, then your experience is telling you to go another level. Level 2 GameDev is where design philosophy, code architecture, critical thinking, art style/direction matters. Try to understand what are problems in the project and design solutions around them. Once you mastered them, you are a technically a senior. Everyone has to go through Level 1 GameDev to reach Level 2 GameDev. Don't need to feel bad about it, you are not alone, we all been through there. Just enjoy the process, level up and have fun. :)

Started my game development journey at 1 January 2023. Wasted my 3-4 months on reading complicated books, Following tutorials(Which was very annoying to copy paste code everytime..) Now,For the past 2 weeks, I'm working on pong game and this is what the real fun and learning is, Basically creating something with your own logic then copy's someone... Now I'm really enjoying game programing with sfml...

As one of these tutorial channels (a small one cause C++ master race), your spot on (granted I have a few playlists on optimization XD). Tutorials should be used to get familiar with something, a starting point. The problem ends up being (more often than not) people using those tutorials and basically copy/pasting from them without learning anything or being able to apply that "skill" elsewhere. For example you want to learn UI so you watch a tutorial on how to make a main menu. Anyone with the ability to self learn will use what they learned from that tutorial to make a HUD and other types of UI, but most will only see it as "now I only know how to make a main menu and cant do anything else, let me lookup how to make a HUD even though its the same process". I have this problem specifically with covering the Online Subsystem in Unreal. It's all an interface so the functions, delegates, and other variables are all the same between platforms, yep people still cant figure it out without handholding going between platforms

Why try and reinvent the wheel though? Why am sitting here figuring out how to code a 3rd person camera when it's already been solved dozens of times over. Unless I want to do something different with the 3rd person camera that requires me doing it all myself, there is no reason not to follow in others footsteps. We all stand on the backs of giants, take advantage of that. Yes you should learn how to use the tools you are using, but you shouldn't ignore solved issues. You should learn how to take the solution and adapt it to your project, how you can modify it if need be. But like I said, reinventing the wheel is just dumb.

Great video. I've been doing game dev for a few years now and it is even my fulltime job. I don't think there is any specific route that someone can follow to success, but it is absolutely true that you cannot just only watch tutorials for all of your core features and expect it to work out. I've seen many people struggle with that and it never works out for them.

Honestly people learn however works for them. To dictate and say one is better then the other doesn't help, that said it's still worth thinking about so good on yah for bringing it up. Personally I like both following and experimenting and even complete works (templates) are beneficial to be pulled apart like you would taking a clock appart etc. As well as I believe the goal of UE is to make it easier for anyone to make games...you don't need to know how UE code works to use UE.

I have been a guy who never searched for any tutorial for feature but i implemented my own, I watch tutorial of others how they implemented that same features after i have already made solution, this way you learn a lot and you also find out other's approach and what would be the best way to refine your version of feature to work properly.

In the other hand, if you are experieced tutorials (I've around 20 years of programming experience), then those "tutorials for newbies" are actually great. Like, I was making some sort of inventory system in my game and I did not know how to implement drag&drop in unity. A 10min tutorial got me enough to make fully featured inventory system by myself. Other example is how to make objects glow in 2D Unity game. Brackeys tutorial was enough for me to get the concept about it being just HDR colors on scene with Bloom post processing effect and I've integrated the tutorial concept as a part of my master shader. Its just a shortcut for documentation and using it this way is great. The weird thing is however, I think they are more helpful to experienced developers that do not know Unity than begginners.

i agree... this is why i only watch them rarely when i really feel like i have no other choice... and then afterwards i usually get annoyed by the lack of people actually answering my actual question, i procrastinate for 2 days, go back to my script, figure it out myself, and laugh maniacally like i'm Light Yagami

I use tutorials frequently, but I typically don't use them as-is. They generally serve as jumping-off points for learning what Unity features already exist and how they can be manipulated. The basic requirement for any design challenge still exists: breaking down big problems into smaller chunks and connecting those chunks together.

I all the creative stuff I do my number 1 rule with tutorials are... Never follow them exactly but listen to them and reference them while making something of your own. Like Pixel art/RPG maker/Synth music/Writing tutorial people are really good with remembering that is their place not to expressly make a step by step guide but to teach the program/methods. So yeah this is a major problem in creative circles thanks for covering it!

as someone in the process of learning front end work I think the best way to learn, at least for me is to watch some tutorials on how that stuff works then, look thru modern websites and find something cool then try to reverse engineer it and I think it applys knowledge a lot

I'm 3 years solo developer without basic programming, I get a lot of information from other developer tutorial, so I agree that they aren't poison if you can modified their code.

Well said. I started with tutorials but made sure that I understood how it works. Now, 3 months in with my game and I seldom check tutorials now and make my code on my own... ☺️

I wrote my first games typed in from magazines on Commodore and DOS. And it's a huge jump today to go from something then to something now. But I think it's important beyond tutorials to understand the core components of a game - your objects (the NPCs, Player, Items etc), building them with good design patterns (Object becomes Item becomes Weapon, etc Object->Character->Player etc). Then once you've mastered the basics, adding in things like input loops, etc. One of the biggest things I've seen in my journey over the years from making games then, Turbo Pascal, C, later C#, Flash, Unity, Godot, etc is realizing that optimization is HUGE. You could have 250-1000 objects on the level, badly optimized, and your game runs poorly. But by using object inheritance, you could easily have a function added to the most basic object that says "IsVisible" that turns off a bunch of checks and suddenly your game performance is fantastic.. You also have multi-threading, and stuff like that too. It's not as big of an issue today on fast desktop PC's but mobile games, if you want to have compatibility that's not just "the latest 2 flagship phones", you will have optimize EVERYTHING.

Simply put, You only learn if you face an obstacle that you cant get over with your current knowledge. If you watch a tutorial, it will just teleport you to the top of the obstacle. Instead only resort to tutorials after exhausting every other option. Also only use tutorials just to get an idea a new perspective. This way you actually learn faster and most importantly, youll have confidence in your knowledge. Thats how i learned physics, mathematics, numerical analysis, programming everything

One of the most important things I learned early, and they never tell you this in the tutorials, is how to read your programming language's documentation. That is what will help you the most if you're using Unity, you're using C#, And the Unity documentation. Once you learn how to do that, you can solve problems for yourself.

I feel into the trap when I started game dev. All aspects of my game were tutorials. Later on I tried to do stuff but didn't know how to even edit my own code because I didn't know what it all meant. Now I barley follow them as I realized that I didn't learn much.

for a little counter argument I learned 3d this way for over 2 years and eventually understood the concepts taught in the tutorials and was able to create most of the 3d content I want 3d character animation environment whatever. I now have a good production pipe line and can problem solve mostly by myself with the occasional tutorial to learn something new.

I’ve just looked up Tutorials when I can’t figure something out and I end up learning g about other stuff in the videos lol

This video is timely! This week I have been thinking of honing my skill as a game programmer and hopefully make a good release but what's holding me back is that I always forgot what I do. This video struct me and I think it helped me progress in my learning.

I have gane development tutorials on my channel and I simply make tutorials on things that I had to figure out on my own and I make tutorials so that another person wouldn't have to go through what I went through when I was trying to learn a specific thing. Through visuals, explanations and demos, my intention is to save a person time and stress for when they attempt to implement what I showed them or they could take what they learned from my tutorials and expand on it. For example, I might show people how to recycle their enemies in their game instead of deleting them. And they could expand on the recycle method. That same recycle method could be used to recycle the clouds in their games or cars or people walking around in the background, etc. And this isvjust an example on how people could expand on what they learned

Great video! I tend to look up tutorials at first to save time, but I’m happy to solve the problem on my own if I can’t find anything. As I start making my own content, I’ll keep in mind how I can show my viewers how to problem solve effectively. Thanks for the insight!

as someone who both follows and creates tutorial, i can agree wholeheartedly with this! I personally watch tutorials as a source of inspiration, not instruction and when I follow something feature specific, i right away try to change up things so I can make sure I'm understanding what i'm doing, not just copying what I see on screen. at the same time, in my comment sections, I see a lot of people without basic troubleshooting and problem solving skills. that's probably in general not something I can fault them for very much but it does show that people will just step by step copy your instructions and then when it doesn't work, have no understanding of what they're doing and game development is really only a small part creating, and a HUGE part changing, experimenting and irritating... all thing you NEED understanding for.. in the same way, I tend to see a lot of people, when they get stuck only ask for help by saying " it doesn't work" , because of course, the people who see an error code and go figure out what that error means and what could cause it on their own, which I'm sure also happens all the time, dont ever comment for help, because they have learned to help themselves. Above all that is what you should learn as a game dev, not any individual bit of code or technique, but the ability to learn and develop an understanding of your situation and the tools you work with, once you get to that point, literally everything is possible now. (which doesn't mean that you'll flawlessly be able to create anything right away, but once you learn how to learn, it's only a matter of finding the info you need.) as a tutorial creator, I do try my best to explain not only what I'm doing but also WHY i'm doing things, but it's a hard balance to land, you never know who might be watching and if you might be under or over explaining things. But my goal personally is always to deliver at least a bit of understanding on top of a specific list of instructions to use. sorry this comment ended up being a bit long but this is very much something I've been thinking about lately too and I think I can bring a somewhat interesting perspective into the discussion here :)

This is actually how I started game dev. I watched tutorials for the first few months but as time went on I just remembered how to implement and to certain things more and more, until the questions were just standard programming questions. Then I started to do things without a game engine, in different languages, etc. This can very well only be my experience though, because I can totally see how a new game developer will just continue watching tutorials for way longer and getting discouraged not being able to do what they actually want. Edit: I just rembered that the reason I might have learnt well that way was because I experimented a bit at every step, e.g. with different parameters, formulas, removing/adding some things, etc. to see how they behave / what they do.

Thank you, im in this situasion. This was an eye opener for me. so thank you very much

a complete video told by both sides of the story, not biased

Generally, I will use tutorials as a base and end up refactoring the entire system to fit my needs. I have gone as far as follow an entire minecraft unity tutorial series, that I ended up refactoring to be multiplayer and more what I wanted.

Then you get so desperated you ask ChatGPT, it helps but then you are stuck talking to him confessing all your problems to him, and he's gonna cry with you

Just starting learning to game dev, think you got point. Watched one tutorial to get basics about unity, now im finishing tutorial's game(flappy bird) by adding things on my own(read, try till its good style). Next are gonna be some good old simple games(pac-man, arkanoid etc) before trying something complicated

This is so underrated. Good video! You earned a sub.

Hey I seem to remember a video concept very similar to this one 😅good stuff, you probably explained it way better than me.

Man i remember when i watched my first tutorial, i was so focused, trying to understand everything and then 30 minutes tutorial turned into 3 hours, the strange thing is that it happened again a 10 hour tutorial turned into 13 days.

So this is what people upload when they realize that making informative content doesn't give as many views as making controversial content :) I'm doing Unity full-time thanks to these guys that helped start and made it look doable

I only ever look for specific things now if I genuinely can't figure out how to implement something, or if I'm not quite sure that something is going to work. Also this same thing happened in university with my classmates, they ended up too reliant on the programming teacher and Unity tutorials and so they were kinda trapped in a cycle of not knowing what to do when a new problem arose.

Keet it up man! It motivates me!

Tutorials are really important, they help u get started, but after u have started and made the first functional project, erase it all and make a new one from scratch, by urself

The way I improved in game dev was the same as when I learned English. I only knew basic sentences that school taught me and from there, I started learning by myself with the foundation I had. When you learn a new language, you usually learn by the book, with formal sentences that people don't use every day. When you learn with a tutorial, you're learning about how to do something specific but you don't know why you're doing it and it might as well be bad practice. Thus, I can only recommend looking at documentation just like you'd read a dictionary, read other people's code like you're reading a discord chat

The problem i have with tutorials are the amount i need to see in order to solve a single problem, for example some time ago i was looking for a way to create a mute sound button for my game, i looked at tutorials and they had similar solutions but applied for their cases alone, some used one single scene for everything, which i didn't, others used GamePrefs which i used but never worked when starting the game. At the end of things i had to create a Frankstein of a mute button which did the job but for the beginning. It was discouraging how i went from trying one solution, watch it fail, try another, see another thing break and at some point i was about to give up, few to no answers in the comments section either, a few of them were "use GamePrefs and put the button to don't destroy, bye" and there i was asking myself how.

I think when starting out for myself using tutorials is great! The problem arises when you're just follow the tutorials and not actually understanding what is happening or why you are doing this to make this happen. I found myself falling into this pattern and started playing around with projects after I had finished a tutorial to turn 1 enemy spawner into multiple enemy spawners or different things. Now im sitting at my desk and coming up with solutions for things I never could have thought of before using logic surrounding the engine but I never could have gotten to this point without a few tutorials here or there.

You're completely correct and as someone making game dev tutorials myself it's something I'm keenly aware of. I think as a learner its important to use tutorials more as a tool to learn the general skills required to begin making things by yourself, and as tutorial creators we have a responsibility to create tutorials that give people a jumping off point to learn more general skills, and don't just show them the very specific way to do one particular thing.

Late to the party, but wholeheartedly agree! I have only few small projects under my belt and maybe one was achieved by just following the tutorial... and I've dropped this project as soon as I finished tutorial. Tutorials are great for learning new tools, engine capabilities, and so on, but going through 10h of "let's make a X game" won't get the project done. I agree.

Thank you for these tips. This was really helpful.

Not only in game dev, many programs I newly started, I need a tutorial to just get a grip on the UI. Then I use less and less as my game isn't the same game the tutorial making no more. I do look for how to do specific functions but I have to know how to modify those to my use also.

How would you recommend learning to code for developing your own games without getting too far down the tutorial rabbit hole?

As a beginner i look up tutorials and understands the concept and try to to do it myself without watching the whole tutorial, this is only possible if you have a good tutorial that explain what we are about to do, if it directly gets into steps then I learn nothing. If I'm completely stuck then only I take up the complete tutorial.

I also started by watching a lot of tutorials and I didnt understand anything and didnt do anything and gave up. But after 2 years of doing nothing I decided to give it another shot but with a different approach. I knew that I wanted to use unity but I didnt knew anything about programming language c# so I decided to learn the programming language first. I started with simple Console Apps with the .NET Framework in Visual Studio. And when I got comfortable with the language and knew the basics I started to learn Unity. It was a challenge, because its a different thing from .NET and learning was slow but I progressed. I watched tutorials but just to get an idea how something gets implemented and I tried to do it by myself or I copy the code and mess around with it. Deleting lines adding more features and so on. This personally helped me to not give up and learn. I also managed to create my first own game and I am still learning it. But it wasnt the only thing that helped me also the documentation was really helpful too!

tutorials are good as a way to learn how things work, from there you need to learn on your own, and you will remember everything you learned.

Optimization is the one thing that i worry about the most regarding game development. I'm currently studying it and planning to start my own personal project before next year, but programming is my weak spot, and i definitely want to make sure it's optimized going in

Tutorials get on my nerves because they don't merely treat you as a beginner of the API (which it should be doing), but many treat you like you've never programmed in your life, so many tutorials are full of crap you have to fast forward through. I notice Unity books do this too. Used to have one where like 4/5ths of the book was "this is how to program... this is what a function is...". I already know that shit!

I really struggle with this, as I feel scared to waste my time on mechanics and different solutions when there could be an easier way. It is the only thing that is reinforced in the community: work smarter, not harder. I feel that if I create something, especially when there is a time limit, that if I can’t complete it in time through experimenting, then I will fail and have nothing to show for it. In the community, lots of people make fun of spaghetti code or say “you should have looked it up,” and it is really hard to find a balance when you are on the clock. Do you try to problem solve a solution for a couple of hours or do you follow a video fully that could be the solution, a dead end (as it can’t be customized) or it just doesn’t work and you haven’t learned. This is why I got stuck on trying to create 2d eyes on a 3d models, that dynamically moved around and worked in unity. Could I have just animated the individual frames and put it on a mesh? Yea. But I want to have a particular vision for the appearance of the character. The last time I tried a similar feature, I completely it my way but ran into a ton of problems, where I had to manual fix every frame. Idk I just don’t feel that it is simple to know when to stop looking for tutorials and when to actually start debugging.

I usually try to find a tutorial for how to make a feature, and than try to impliment that into my game. If I can't find one, than I just have to spend like a week or two figuring it out.

Omg, im glad that i didnt fall on this tutorial trap, back in 2021, i started using an engine by watching tutorials, and now i know everything about it 😅

TFW suddenly game development-videos go the full Sir Ken Robinson-route out of nowhere XD

That's why the courses/academia exist. To learn how to think and face any kind of project. To create a solid architecture for any software project. Last year I prepared a course to teach students how to start thinking about creating that solid structure for they projects to grow. Tutorials are great when you have a doubt about something specific, but as a foundation to create software is the most horrible think you can do. Eventually you end up with a bunch of spaghetti code that can barely hold itself together.

This guy just said what most people should know. If you don't, then that's a whole nother tutorial you need.

It is the same like developing enterprise software like apps, websites or whole complex systems for administering a companies assets. Tutorials are good to build a basic understanding but that won't be enough for building a fully functional software. You have to search for small project ideas (e.g. the famous Todo app), try out and use the knowledge and work your way up to bigger projects (like a full website with login, registration, a chat, sending friend requests etc.) If you build something like that from the ground up then you will have enough to do for months! Through failing in each and every project you will learn more than only relying on tutorials. And at some point you developed so much that you know what components are used in each and every software each and every time. At this point you will get faster in development and only very specific problems will be challenging and take a lot of time.

I hope the algorithm favors your videos

Only the very basic unity tutorials are the best. In fact when starting out, making the exact game as the tutorial can be useful because seeing code actually work for yourself can encourage you. But once you're done with a couple of tutorial series and want your own game made - stay away from tutorial series. Tutorials are specifically made with speed and simplicity in mind. They don't talk about the very detailed mechanics actual games have. For that , you gotta play games and find inspiration. Learn to code by writing your own code from imagination.

I’m currently having this problem. While I find game maker videos on specific things and they go a little in depth about certain aspects, they don’t come back with those aspects.

What exactly did Brackeys do to get shit on the thumbnail? I swear this is the third video that uses his image as the "tutorials bad" man

It's basically the difference between following a recipe to bake a cake vs going to culinary school to learn what the chemistry behind that cake is

Im still learning unity but instead of following tutorials i would instead learn the to implement the system(cinemachine/input system etc) and learn unity built in functions for scripting. I think thats giving me the best results

I think tutorials are a great starting point to experiment - it should never be the exact solution to your problem but it can be a factor. Id agree with your title if it says "why game dev tutorials can poison your progress".

I think that in order to have more creative tools its better to search functionality tutorials instead of "full game tutorial", for example if I know how a inventory function works i will probably be able to do create a new one, mentally design it, and make it in order to meet my expectations insted of just "recycling" the functions of other people, would you agree?

I think this is true for any kind of tutorial or thing you're trying to learn. In coding it's called "tutorial hell" where you learn how to complete the tutorial but never take anything away from it. With art there are just so many methods and styles that no one can really teach you how to make art just like how you want to make art.

idk if Unreal has any tutorials but Unity provides FANTASTIC tutorials on their site that helped be learn the engine greatly, haven't touched unity since I started learning Blender but I can still do most of the tutorials by memory at this point

The problem is that new folks aim for their "dream game" instead of making simple games with 1 or two basic versions of mechanics/tools that you they don't understand to learn the basics and then move on to more complex development.

I think this kind of learning is okay if you aren't intending to make a masterpiece - it's fine for a proof-of-concept version to take to a professional developer, for example.

I did and do follow tutorial because Im in the learning process. But before watching the video, Im trying to do the code myself and then see how the instructor is doing the code. Most of the time I can do it myself. But sometimes I learn something new

I have graduated from watching dev tutorials to watching meta videos about tutorials.

write down every core feature required by your game. find a youtube video tutorial for each one . make your game.

I just started using Unity, and i tried to combo chatgpt with it and it works perfectly. ofcourse i get some error codes here and there when it comes to scripts, but i just copy paste it into the ai and it explains how to fix it. it also answers questions i have, with no issues

Needed this video. The best way to learn is making easy games that already exist and bringing your new skills to the next project. I made rock paper scissors and now I'm making a card game. But I'm getting stuck so I'm gonna make tic tac toe to learn some new things. One day I asked myself, if Rome wasn't built in a day, nor were the current Nintendo games, so why am I trying to make complex games when I haven't learned to get there by making pong or super Mario bros? Start by remaking stuff that already exists to learn the engine, then make the games of your dreams with what you learned.

this is why i wanted to learn programming first. even tho i knew the basics, but when using that in game engines such as unity and unreal, its like everything ive learned didnt work. or maybe its because i only know the basics in programming. which is why im now tryna learn the programming tutorials instead of the "how to" tutorials. hopefully thatd be better in understanding what im/ill be doing. because like you said majority of time is problem solving, which is true

Imo watching a single tutorial course, and then know the basics and then look up whatever you need

You have to start somewhere and beginners watch tutorials to start learning. Once the become better they watch less tutorials. This shouldn't even be a video. Edit: seems that I was wrong and this video raises some good points to help some aspiring devs

So the best way to learn from 0, is to learn the basics with tutorials and then start practicing on my own (for example in gamejams)?

as someone who's had multiple attempts at creating a game, all of which (until now) ended at the "tutorial, open unity then give up" stage, i find that the issue with a lot of tutorials is the fact that, while they do make things as simple as they can, they still don't go over EVERYTHING. yeah, sounds stupid, but what i mean by that is that all code is alien to a beginner. why do you use this statement here? why is there a command made up of 3 words which seemingly make no sense, and what does it do? why do we have to use that? when do i use " ", , () and why? they don't explain these. i found one guy on yt who did explain, and nothing else. he explained the most used commands, what they mean and what they do, and it was the most useful thing ever. it reminded me to go back to the basics (scratch, "programming" on paper), and think of every aspect of a feature, which then leads to an idea on how to make it happen. if all tutorials were like that, treating you as an actual beginner learner rather than a copy machine at school, then they'd lead to more productive things. the issue probably comes from the fact that those who make the videos are expert programmers who forget or just assume things make sense for everyone, when it'd be easier if they stepped down their level a little. still though, i appreciate the people who take time out of their day to educate others, no matter how well, because it's still information. that's my two cents

People that think like you just described should not be making games in the first place at all

You could have made the same point without trying to discredit prominent figures of The Game Dev community I've never met a developer that said let's not look at any documentation asked for help or watch a video and let's brute-force this problem

usually i just need the tutorial to show me how something works practically then i go off and alter it and use it for my own stuff.

What you said at 2:20 pretty much covers it: If you don't know why you're using what you are, you'll never be able to learn how to solve more general problems. But that doesn't mean tutorials poison progress - you just have to watch them with that in mind. Every tutorial should be a three part process. 1) Watch them and follow along to get the ideas, syntax, and "muscle memory". 2) Try to recreate the project yourself without referring to the original tutorial/project. 3) Try to improve on it by building your own features using what you learned. As you quickly mentioned, you see the same thing teaching math in schools/universities. People are so used to following a procedure without knowing why. Doing a math major is a great way to learn the instinct to ask why and learn HOW to ask why. Finding ways to answer your question given a set of certain building blocks. As all mathematical theorems are built upon smaller propositions which can be proved straight from the axioms of your logical system. Changing those building blocks (axioms) and you get a different system which might be more/less efficient or allows you to prove different results that might not have been previously possible. This extends well to programming - theoretically all you should need to master a program is its documentation!

Honestly, that's what bugs me about GDevelop tutorials and the forums. Every time I look up a tutorial or ask a question on the forums, the answer I receive is always focused more on CONVENIENCE instead of OPTIMIZATION, which is annoying if you're making a bigger project I don't want to do it the easy way, I want to do it the smart way At this point, I end up learning more by reverse engineering games and picking through the code rather than looking up a tutorial. That way, I can see how a full game is optimized, which is super helpful, and tbh, something that I recommend to every aspiring game developer

This is how machine learning AIs learn and why I think MLAIs are overhyped

Good point - even if you're just doing gamedev as a hobby, you might want to do it right

Ouch. Followed an endless runner tutorial as I believed it would serve as a great foundation. Got to the end - working fine. Now to start extending, I wanted to serve a range of 'environments' like industrial, forest etc. Uhoh!!!! Not possible within this design, just the same 'block' over and over - very efficient, but hmm a little limited.... Initially slight disappointment, a little time wasted to see if it was possible to achieve, then classed the week as an investment in techniques learning etc. Quickly decided to now use the 'gained knowledge' and start from scratch with my own structure. So I fully agree, one should use them by all means but not think they'll be extensible/customisable into your own game...great video - and for me at this point comforting!!!

I started watching game tutorials and failed immensely in being able to understand. You can follow every step but you won’t remember any of it.

1:19 bro its ironic i followed the same Tutorial and after the comoletion i wanted to add things too it but wasnt able too just like this guy says😂

I would try to find answers in the official documentation before watching tutorials. Tutorials sometimes don’t explain every line of code, how they know these lines of code are necessary, where they got the information from.