What I learn is knowing that engine is capable of ruining your life, wasting time learning tutorials for years but then suddenly Tax slap in your face.
The most difficult thing for me at the beginning was the terminology. For example, I remember couldn't find the documentation for "Raycast" because I didn't know that it was called a Raycast. The videos on the Unity website have always been a pretty good balance. They just about get you going on your own, but not more. The kind of "Here's how you make a ball. Here's how you make it roll. OK, bye!" XD
thank you for the video. I have been following tutorials and have experienced similar to what you have, I just haven't learnt anything. I also appreciate how clear you are as I now understand how to tackle this problem and start using resources on google and Unity's documentation. really appreciate it!
i dont really agree, saying tutorials are bad as a blanket statement is too general. yes some are bad, some are good and few are great. Ive been a software developer for nearly 20 years and i still watch tutorials on a daily basis. Now im not watching them to copy what they are doing, i watch them to gain a small insight on one or 2 specific things im looking for. I know plenty to navigate on my own and just need to track down the process on certain things from time to time. sometimes its take a few videos to find that nugget of useful info. I was traditionally trained in college and one thing a professor said that has stuck with me my whole career is this: "Everything you learn today will be irrelevant in 5 years. You have to learn, how to learn." Finding info quickly is a skill that takes time and practice. Tutorials are great, not to copy and paste but learn how to benefit from bits of info. So keep watching, watch often and a lot, absorb it ALL!
I'm an Unreal dev and not a Unity one, but I only use tutorials as a last resort if I really am stuck on implementing a specific thing. Like if I want the character to be able to move down underwater or have a basic notifications system that I can modify for my current setup. I learn from other sources for the most part.
I agree with this 1000% when I got into programming I never really self taught myself the way I did art. After actually looking things up on my own and reading documentation I started getting leagues better at programming and also would remember things. My number 1 rule was stop looking at videos and get all my answers from unity scripting api. Most people don't put what they've learned into practice since whats the point if its already done? either way most of these tutorials do give you the solution but not the experience.
You're spitting facts here. I'm barely beginning my C# journey and already understand that if I continue copying I'm going to be too reliant on other sources to write code other than myself.
I followed this and it really really works just changing the name of variables and classes helps us to stay on the path of learning and not on the path of just copying and pretending that yes I did it!!!! Thanks bro
I have learned more coding in the last month or so using ChatGPT then in the past few years, the ability of it to answer a question that is asked like a total noob is astonishing. and it can keep building and expanding on a single subject as well as generate infinite examples, as well as examples that closely relate to what your working on. I would 100% recommend anyone learning to ask ChatGPT questions, I have found it to be a far better recourse than Stack overflow or even the Unity docs.
While I agree that most of the tutorials could be much better, I believe by saying that "you should be implementing code conventions and/or software architecture right from the get go" you're missing the point of these things. Code conventions are there for a reason, so is different software architecture things. And that reason is 1) to be comfortable and sensible to work with and 2) to support change. If the code tutorial presents is subpar to industry standards, but it gets the job done - that's great for new developer. They don't need all that overhead of thinking ahead about their work comfort in the future, they just need to make box move on the screen. And later they will inevitably realize that their code is hard to modify, their variables are named poorly and don't make sense, and everything takes too much time. So they turn to industry standards and learn the solutions. What you do in this video is warn novice developers about stuff they haven't seen yet. Putting forward solution to a problem they don't have yet, or don't realize is a problem. I personally believe people should start from tutorials, write shit code, realize that they messed up and fix it. This way they will not only learn HOW to use conventions, but also, most importantly, WHY to use them, their real value and application. Instead of "my code works already, but I must use this and that because everybody is talking about it and using it", make it "I had this problem, and this convention solves it, so I will use this thing". This is how I learned, and since you said you got stuck in tutorial hell, I guess you did too. So what's wrong with learning that way?
THIS exactly it... where I'm at... I truly understand what you are saying... for years I have tried to learn 2d gamedev via Gamemaker or Defold tutorials.... but I never able was to fully understand them... I can move the box and do collision...but sometimes it ask too many parameters I dont understand but I still use it.... now I'm going one level deeper which is to code a game using just Love2D.... its still incredibly simple from something coding in bare C++ but it has more depth and mostly satisfies my need to understand exactly why certain things are like that
I absolutely agree. I do think some talk about good practice sprinkled in so that new devs won't struggle so much to pick up new habits later, but I think a lot of programmers try to frontload it into the first couple lessons of a series and it makes the whole process so overwhelming. At the beginning, new devs need to know how and why some code works for basic development and then can work on bettering their practices later. I think of it kind of like having some rough drafts of a book or paper and then improving it later on once you know how to actually get words in the right order.
The best thing that I did was buying a course with a good instructor (because it makes a WHOLE difference), tutorials are good to know what is possible to do but they will not teach me the fundamental of how or why is possible to do that certain thing
That's why I used Jimmy Vegas, he has scripting video on one subject, like walking into a trigger and a sound playing I think that if you only have single guides on one subject than you can mash them together to make a game
While i agree people shouldnt get stuck i think beginners should get that dopamine train rolling through quick wins and tutorials. Personally i think im at the point where im leaning on tutorials and chatgpt too much and my codes getting clunky. So its naturally time to start taking it seriously.
I completely agree! My main point with the video was that you need to leave the tutorial comfort zone as soon as possible to make sure you grow as a programmer. Tutorials are a great starting point, but they are also dangerous. I wish you all the best on your programming journey!
I don´t realy agree sire... The Point is, you need to understand C#!!! With a good basic in this, you are able to learn from others, cause you are able to understand what the ppl are doing and why! After that comes the part, where the most than struggle:"They are not able to think abstract and so not able to find solutions for the problems in they projekt!"
I found this tutorial where the guy explains how everything works and why it does this, leading to me learning how to make the player jump, how to make it that you can’t spam jump etc.
there's a lot of bad tutorials where all they do is paste code into a text editor and do a code walkthrough very fast. You never understand what they are doing. What's better are courses where you work through projects along with the video, and you start to understand what's going on. Also doing stuff outside the course by yourself will cause you to learn things. There are a lot of good youtube tutorials where they explain it better and show you exactly what's going on. I've learned a lot from those. It's all about understanding how to use what you learn on something new.
A tip to test yourself is, most courses are split into lessons and start with explaining what they will work on that lesson. Pause the video and try to do it yourself first, treat it like an assignment then afterwards, you can resume and see if you did it. Also learn better coding methods, some of these tutorial use poor practice and I'll usually use better methods in place of what they want
The way i see tutorials is that its not what they teach you, its what else is taught in disguise in that tutorial. For example the tutorials shows you the code to move left and right in a 2d game to dodge obstacles falling down, but it doesnt each you or give you the code to move up and down. But thats how you have to see it and figure out if you can use similar rules and code to move the player in a different direction whether its replacing the word horizontal to vertical and mapping it to the w or s key. Thats how you really force yourself to learn more than mimic. A tutorial isnt an answer althought some can be, but its just another way to do the same thing. If the tutorial shows you how to move the players position to another via transform and collision detection, you could probably figure out how to make an infinite road without word-for-word google searching.
Totally agree on unity tutorials teaching bad coding habits, for the most part. I've been watching a lot of them to pick up the systems available and try by consensus to get an idea of how they're used. But I also follow some channels of actual good coders who are using good encapsulation/SOLID techniques to get to a better path. But you're right, it then takes longer to actually make the game, and that's something that's skewed in these videos. What is short is making concepts - making a full game takes forever, a large time investment shortcutted only by paying for things that make it quicker and easier, like assets.
The vast majority of tutorials will have better code quality than what a beginner will come up with on their own and there's no point to reinvent the wheel. If you dont use ChatGPT and frequently borrow code then the only thing you're doing is wasting your time. Learning how to borrow, understand and adapt code is fundamental to being a good programmer.
I go for courses rather than tutorials. My method is to do a section of the course, then put it away until I take what I learned and apply it to one of my own projects.
@@trevorfranks69 that is incorrect. A tutorial is geared towards showing how to do one thing. A course is a more general series of lessons geared towards teaching a rounded understanding of a subject.
A good way to learn is, is my fav method called "fuck around, to find out, to find out and fuck around" so basically, find out how they do it, and then play around with it to understand it
@@globox-dev if i may, i am studying to make my dream game, atm im learning animation both 3D and 2D, any recommendations on what books can help me in coding??
There's a lot here that i agree with, but there's quite a bit that i disagree with. I believe tutorials are ESSENTIAL when you're first starting because otherwise it's overwhelming and you dont understand the common use cases. The trick i believe is taking these tutorials and expanding on them. for example, like how you mentioned renaming the variables, or trying to recreate something you did before but referencing the code rather than a video. And then after you've become comfortable with the terminology, code structure, then to start learning proper coding practices. But i get the point of this video and thats to prevent using tutorials a s a crutch. But it's a journey
I feel like i been stuck in like tutorial devlog hell...havent started dont know where ti start keep seeing too many videos saying dont copy and paste and too many saying its good to copy n paste at first and its just like aaaaaaaaaaa
Gonna be honest, I opened up Unity, saw it's UI, closed the program, and have never opened it since. Unsure why since I wanted to use it and was aware of the difficulty.
This video is a little interesting, because I disagree in the fact that you can learn things from a tutorial IF you attempt it your self and follow on parts your stuck on. Don't just blindly follow a tutorial as that will get you no where.
That's a really cool video and I'm sure it will sure it will blow up soon :3 I guess we need to debate about the tutorial usefulness because after watching a lot of tutorial i became autonomous and i'am writings code byself ... Like you've say it's not about the tutorial but more about your mindset, also we should have more tutorial that explains you how something works and not simply showing the code and speedrunning everything
Exactly! I really want tutorials which show the different things in Unity and how they can be used. I get super overwhelmed with most tutorials because a dev will write some code and say "don't worry about it," but if I just paste it in I will have no idea how to use it in the future, how to debug it, or even what it really does. I struggle a lot with grasping documentation, since I'm still in the early stages of game dev and don't have tons and tons of programming experience. I like knowing how and why things work, instead of just how to do x or y.
The most helpful tutorial series for Unity I've come across is Catlike Coding. It's basically a collection of books online and Jasper uses many of Unity's advanced features (Jobs, URP, shader graph) and covers concepts that you would see in university courses (mathematic modelling and graphics rendering). He also teaches concepts and best practices that can be used in your own programs without giving you truly complete games.
ngl this is false I learnt untiy from watching lots of tutorials and than after some time edting the scripts been a agamedev for 5 years now so don't give up watch those tutorials and get better good luck !
Would Not say all Tutorials are useless. But agree Theres also alot crap on RUclips and co. But i mean its Like the Most creators dont Care about. They See a Tutorial, Copy a Tutorial, Change the Tutorial abit , reupload it as its own. And of course after 5 Times Copy Change Paste Comes Something crap Like Out. Actually rlly sad. I rlly do Not Know how often insaw my own Tutorials already copied by Others on RUclips haha
I have starting to learn C# like 2-3 months ago, in the tutorials I copy the Code but I try to understand how does every line work searching online what does everything mean and how and why affects the code My only issue is that I don't know what should I do to really understand coding, like ok I know what a variable is, what is a float, boolean, etc but how do I really use them? How can I create something from Scratch? If I start from Scratch like an empty visual studio I have no idea what to do to create something basic Any advice? I know that I learn from testing and failing but how can I test and fail with something that I don't even know how to start? I really like how coding works but idk how to go step by step, is there any web or something that gives you like excersices or something like that? Like hey resolve why this Code is wrong or fix this and stuff but for begginers Great vídeo, I was having the same feeling as you said in the video, following every step from tutorials you just copy everything that is being written in the tutorial Sorry for my grammar I still learning english :P
I love seeing more people take the initiative to learn how to code. And for a complete beginner, understanding the code you get from tutorials is a significant first step. Going from following a tutorial to building something from scratch is a giant leap for most, if not all, beginners. It will take time, but to deepen your understanding of code at your stage, I suggest experimenting with the code from the tutorials you are following. Change a variable or even type, remove a line, and see how it affects the program. Does it break? Did the output change? How did it change? Why did it fail? Since starting from scratch is out of reach, the best middle ground is to work with pre-existing code. Try adding a feature not mentioned in the tutorial. This requires you to navigate the tutorial code and understand most of it to add something without breaking what is already there. And if you break something, it's not a big deal since you now have a self-inflicted coding challenge to solve. When creating something from scratch, starting with a clear goal or problem to solve is helpful. For example, you could create a simple calculator or a program that generates random passwords; if you are more interested in game development, it could be as simple as making a square move right and left and nothing more. This will give you a framework and help you focus your efforts. But most importantly, it gives you an end goal. It allows you to finish something. This is great for your motivation to learn early in the learning stage and gives you a lot of momentum to go on to a new, slightly more demanding challenge. As for resources, many online platforms offer exercises and challenges for beginners. Codecademy, Khan Academy, Codewars, and Udemy are all great places to start. Remember that learning to code is a process, and making mistakes and failing is okay. Keep practicing and asking questions, and you'll gradually develop the skills and knowledge you need to create projects from scratch. P.S. Don't worry; your English skills are excellent, and you will only get better with time :)
Eh I want to say as a educator this is terrible advice especially within in the creative field that is game development. But alas this is youtube anyone with a platform can give their advice an opinion and you don't need a degree and multiple years of education to teach people. Some make some valid points but hammer on some pretty damaging things such as teaching people that "copying" is bad. It isn't. It's how we as humans learn from the get go. It is not a bad thing to copy. Also just because someone is copying doesn't mean they aren't actively learning and understanding. There are plenty of tutorials which teach people poorly and simply don't explain the reasons for what certain things are done and they simply create something not with the intent to teach their audience but to gain a viewership, get content out and continute their grind.
much information on the internet is unstructured in terms of learning. adding to that is the conflict of interest between video lesson structure and monetization. very few viewers actually have the time to sit down and watch an hour long lesson while taking notes, pausing the video to solve the questions by themselves, etc. this means the real money is in entertainment, not in producing useful learning content.
I think the main thing he missed out is everyone learns differently, a tutorial can be great for people who learn from watching, but some people are more practical.
What I learn from tutorials is knowing what the engine is capable of. Learning there is a tool for this and a tool for that.
Y
What I learn is knowing that engine is capable of ruining your life, wasting time learning tutorials for years but then suddenly Tax slap in your face.
The most difficult thing for me at the beginning was the terminology. For example, I remember couldn't find the documentation for "Raycast" because I didn't know that it was called a Raycast.
The videos on the Unity website have always been a pretty good balance. They just about get you going on your own, but not more. The kind of "Here's how you make a ball. Here's how you make it roll. OK, bye!" XD
lmao bro ithink you meant "ra cist"
@@fl3xr lmao bro i think you meant nigg-
@@fl3xr waiting for that like still, huh
@@KapybaraKSPyep
@@fl3xr it’ll come eventually
so that means that i gotta learn scripting language by myself with no help? nah bro, you're trippin
thank you for the video. I have been following tutorials and have experienced similar to what you have, I just haven't learnt anything. I also appreciate how clear you are as I now understand how to tackle this problem and start using resources on google and Unity's documentation. really appreciate it!
i dont really agree, saying tutorials are bad as a blanket statement is too general. yes some are bad, some are good and few are great. Ive been a software developer for nearly 20 years and i still watch tutorials on a daily basis. Now im not watching them to copy what they are doing, i watch them to gain a small insight on one or 2 specific things im looking for. I know plenty to navigate on my own and just need to track down the process on certain things from time to time. sometimes its take a few videos to find that nugget of useful info. I was traditionally trained in college and one thing a professor said that has stuck with me my whole career is this: "Everything you learn today will be irrelevant in 5 years. You have to learn, how to learn." Finding info quickly is a skill that takes time and practice. Tutorials are great, not to copy and paste but learn how to benefit from bits of info. So keep watching, watch often and a lot, absorb it ALL!
I'm an Unreal dev and not a Unity one, but I only use tutorials as a last resort if I really am stuck on implementing a specific thing. Like if I want the character to be able to move down underwater or have a basic notifications system that I can modify for my current setup. I learn from other sources for the most part.
can you please drop some opf the other sources you use thanks?
I agree with this 1000% when I got into programming I never really self taught myself the way I did art. After actually looking things up on my own and reading documentation I started getting leagues better at programming and also would remember things. My number 1 rule was stop looking at videos and get all my answers from unity scripting api. Most people don't put what they've learned into practice since whats the point if its already done? either way most of these tutorials do give you the solution but not the experience.
Very high quality video, I didn't even notice I wasnt watching some 200k subs channel. Keep up the good work👌
Thanks, will do!
You're spitting facts here. I'm barely beginning my C# journey and already understand that if I continue copying I'm going to be too reliant on other sources to write code other than myself.
I followed this and it really really works just changing the name of variables and classes helps us to stay on the path of learning and not on the path of just copying and pretending that yes I did it!!!!
Thanks bro
Glad it helped!
I have learned more coding in the last month or so using ChatGPT then in the past few years, the ability of it to answer a question that is asked like a total noob is astonishing. and it can keep building and expanding on a single subject as well as generate infinite examples, as well as examples that closely relate to what your working on. I would 100% recommend anyone learning to ask ChatGPT questions, I have found it to be a far better recourse than Stack overflow or even the Unity docs.
Yes I Do The Same
While I agree that most of the tutorials could be much better, I believe by saying that "you should be implementing code conventions and/or software architecture right from the get go" you're missing the point of these things. Code conventions are there for a reason, so is different software architecture things. And that reason is 1) to be comfortable and sensible to work with and 2) to support change.
If the code tutorial presents is subpar to industry standards, but it gets the job done - that's great for new developer. They don't need all that overhead of thinking ahead about their work comfort in the future, they just need to make box move on the screen. And later they will inevitably realize that their code is hard to modify, their variables are named poorly and don't make sense, and everything takes too much time. So they turn to industry standards and learn the solutions.
What you do in this video is warn novice developers about stuff they haven't seen yet. Putting forward solution to a problem they don't have yet, or don't realize is a problem.
I personally believe people should start from tutorials, write shit code, realize that they messed up and fix it. This way they will not only learn HOW to use conventions, but also, most importantly, WHY to use them, their real value and application. Instead of "my code works already, but I must use this and that because everybody is talking about it and using it", make it "I had this problem, and this convention solves it, so I will use this thing".
This is how I learned, and since you said you got stuck in tutorial hell, I guess you did too. So what's wrong with learning that way?
THIS exactly it... where I'm at... I truly understand what you are saying... for years I have tried to learn 2d gamedev via Gamemaker or Defold tutorials.... but I never able was to fully understand them... I can move the box and do collision...but sometimes it ask too many parameters I dont understand but I still use it.... now I'm going one level deeper which is to code a game using just Love2D.... its still incredibly simple from something coding in bare C++ but it has more depth and mostly satisfies my need to understand exactly why certain things are like that
I absolutely agree. I do think some talk about good practice sprinkled in so that new devs won't struggle so much to pick up new habits later, but I think a lot of programmers try to frontload it into the first couple lessons of a series and it makes the whole process so overwhelming. At the beginning, new devs need to know how and why some code works for basic development and then can work on bettering their practices later. I think of it kind of like having some rough drafts of a book or paper and then improving it later on once you know how to actually get words in the right order.
@@theConcernedWyvern I agree so much with this !
The best thing that I did was buying a course with a good instructor (because it makes a WHOLE difference), tutorials are good to know what is possible to do but they will not teach me the fundamental of how or why is possible to do that certain thing
That's why I used Jimmy Vegas, he has scripting video on one subject, like walking into a trigger and a sound playing I think that if you only have single guides on one subject than you can mash them together to make a game
While i agree people shouldnt get stuck i think beginners should get that dopamine train rolling through quick wins and tutorials. Personally i think im at the point where im leaning on tutorials and chatgpt too much and my codes getting clunky. So its naturally time to start taking it seriously.
I completely agree! My main point with the video was that you need to leave the tutorial comfort zone as soon as possible to make sure you grow as a programmer. Tutorials are a great starting point, but they are also dangerous. I wish you all the best on your programming journey!
@@globox-dev Totally, and your point gave me some good things to think about. So a valuable video from my perspective.
I don´t realy agree sire...
The Point is, you need to understand C#!!!
With a good basic in this, you are able to learn from others, cause you are able to understand what the ppl are doing and why!
After that comes the part, where the most than struggle:"They are not able to think abstract and so not able to find solutions for the problems in they projekt!"
I found this tutorial where the guy explains how everything works and why it does this, leading to me learning how to make the player jump, how to make it that you can’t spam jump etc.
there's a lot of bad tutorials where all they do is paste code into a text editor and do a code walkthrough very fast. You never understand what they are doing. What's better are courses where you work through projects along with the video, and you start to understand what's going on. Also doing stuff outside the course by yourself will cause you to learn things. There are a lot of good youtube tutorials where they explain it better and show you exactly what's going on. I've learned a lot from those. It's all about understanding how to use what you learn on something new.
A tip to test yourself is, most courses are split into lessons and start with explaining what they will work on that lesson. Pause the video and try to do it yourself first, treat it like an assignment then afterwards, you can resume and see if you did it.
Also learn better coding methods, some of these tutorial use poor practice and I'll usually use better methods in place of what they want
The way i see tutorials is that its not what they teach you, its what else is taught in disguise in that tutorial. For example the tutorials shows you the code to move left and right in a 2d game to dodge obstacles falling down, but it doesnt each you or give you the code to move up and down. But thats how you have to see it and figure out if you can use similar rules and code to move the player in a different direction whether its replacing the word horizontal to vertical and mapping it to the w or s key. Thats how you really force yourself to learn more than mimic. A tutorial isnt an answer althought some can be, but its just another way to do the same thing. If the tutorial shows you how to move the players position to another via transform and collision detection, you could probably figure out how to make an infinite road without word-for-word google searching.
Totally agree on unity tutorials teaching bad coding habits, for the most part. I've been watching a lot of them to pick up the systems available and try by consensus to get an idea of how they're used. But I also follow some channels of actual good coders who are using good encapsulation/SOLID techniques to get to a better path. But you're right, it then takes longer to actually make the game, and that's something that's skewed in these videos. What is short is making concepts - making a full game takes forever, a large time investment shortcutted only by paying for things that make it quicker and easier, like assets.
The vast majority of tutorials will have better code quality than what a beginner will come up with on their own and there's no point to reinvent the wheel. If you dont use ChatGPT and frequently borrow code then the only thing you're doing is wasting your time. Learning how to borrow, understand and adapt code is fundamental to being a good programmer.
Why the volume is so low
I go for courses rather than tutorials. My method is to do a section of the course, then put it away until I take what I learned and apply it to one of my own projects.
Courses are the same as tutorials.
@@trevorfranks69 that is incorrect. A tutorial is geared towards showing how to do one thing. A course is a more general series of lessons geared towards teaching a rounded understanding of a subject.
Tutorials helped me a lot. I published a game on Steam. I don't think they're your end point, but I'm okay with them being a starting point.
What's the game called
@@RileyHighBerg It's called Boxed-In. It's a terrible game.
A good way to learn is, is my fav method called "fuck around, to find out, to find out and fuck around" so basically, find out how they do it, and then play around with it to understand it
I completely agree!
@@globox-dev hope to see more vids!! youre doing amazing!
@@globox-dev if i may, i am studying to make my dream game, atm im learning animation both 3D and 2D, any recommendations on what books can help me in coding??
There's a lot here that i agree with, but there's quite a bit that i disagree with. I believe tutorials are ESSENTIAL when you're first starting because otherwise it's overwhelming and you dont understand the common use cases. The trick i believe is taking these tutorials and expanding on them. for example, like how you mentioned renaming the variables, or trying to recreate something you did before but referencing the code rather than a video. And then after you've become comfortable with the terminology, code structure, then to start learning proper coding practices. But i get the point of this video and thats to prevent using tutorials a s a crutch. But it's a journey
I feel like i been stuck in like tutorial devlog hell...havent started dont know where ti start keep seeing too many videos saying dont copy and paste and too many saying its good to copy n paste at first and its just like aaaaaaaaaaa
very good review about tutorials i usually whats them understand concept of things and see how people make things so i can adapt my stuff
Is the reading documents good?
Great advice! Any specific books you could recommend?
Yeah, I have left a few links to some of my favorites in the video description.
I hope you continue making videos❤
Tutorials they gives you ideas and your job have to implement with the right way.
if you talk to the right of your microphone de audio sounds louder on the right ear
Gonna be honest, I opened up Unity, saw it's UI, closed the program, and have never opened it since. Unsure why since I wanted to use it and was aware of the difficulty.
This video is a little interesting, because I disagree in the fact that you can learn things from a tutorial IF you attempt it your self and follow on parts your stuck on. Don't just blindly follow a tutorial as that will get you no where.
Nah bro you forgot something, if you don't copy the whole tutorial and watch it for the system its better, and also to understand, LEARN CODING FIRST
What c# book do you recommend?
You should make the video quieter, I could almost hear something.
Unity's dirty little secret is it's not possible to follow SOLID principles in Unity.
Yeah, learning OOP before Unity isn't all that helpful and probably confusing to beginners. If all you want to do is make games then just learn Unity.
This applies to all fields of study. Massive 🔥
That's a really cool video and I'm sure it will sure it will blow up soon :3
I guess we need to debate about the tutorial usefulness because after watching a lot of tutorial i became autonomous and i'am writings code byself ...
Like you've say it's not about the tutorial but more about your mindset, also we should have more tutorial that explains you how something works and not simply showing the code and speedrunning everything
Exactly! I really want tutorials which show the different things in Unity and how they can be used. I get super overwhelmed with most tutorials because a dev will write some code and say "don't worry about it," but if I just paste it in I will have no idea how to use it in the future, how to debug it, or even what it really does. I struggle a lot with grasping documentation, since I'm still in the early stages of game dev and don't have tons and tons of programming experience. I like knowing how and why things work, instead of just how to do x or y.
@@theConcernedWyvernTHIS IS ME
The most helpful tutorial series for Unity I've come across is Catlike Coding. It's basically a collection of books online and Jasper uses many of Unity's advanced features (Jobs, URP, shader graph) and covers concepts that you would see in university courses (mathematic modelling and graphics rendering). He also teaches concepts and best practices that can be used in your own programs without giving you truly complete games.
But other than that, yes - follow what is being said here.
Effective thumbnail
for fucks saaaaake, i just started writing a script on this subject... oh well, great video!
Ben Cloward : Hold my shaders 🤣🤣
you change my life...
lets collab 👉👈
Sure, I would be happy to collab with you. Please send me a message on discord.
Book recommendations please
If you understand what you are coding then by time you might learn
I like your Rb hat
ngl this is false I learnt untiy from watching lots of tutorials and than after some time edting the scripts been a agamedev for 5 years now so don't give up watch those tutorials and get better good luck !
Would Not say all Tutorials are useless. But agree Theres also alot crap on RUclips and co. But i mean its Like the Most creators dont Care about. They See a Tutorial, Copy a Tutorial, Change the Tutorial abit , reupload it as its own. And of course after 5 Times Copy Change Paste Comes Something crap Like Out. Actually rlly sad. I rlly do Not Know how often insaw my own Tutorials already copied by Others on RUclips haha
I have starting to learn C# like 2-3 months ago, in the tutorials I copy the Code but I try to understand how does every line work searching online what does everything mean and how and why affects the code
My only issue is that I don't know what should I do to really understand coding, like ok I know what a variable is, what is a float, boolean, etc but how do I really use them? How can I create something from Scratch? If I start from Scratch like an empty visual studio I have no idea what to do to create something basic
Any advice? I know that I learn from testing and failing but how can I test and fail with something that I don't even know how to start?
I really like how coding works but idk how to go step by step, is there any web or something that gives you like excersices or something like that? Like hey resolve why this Code is wrong or fix this and stuff but for begginers
Great vídeo, I was having the same feeling as you said in the video, following every step from tutorials you just copy everything that is being written in the tutorial
Sorry for my grammar I still learning english :P
I love seeing more people take the initiative to learn how to code. And for a complete beginner, understanding the code you get from tutorials is a significant first step. Going from following a tutorial to building something from scratch is a giant leap for most, if not all, beginners.
It will take time, but to deepen your understanding of code at your stage, I suggest experimenting with the code from the tutorials you are following. Change a variable or even type, remove a line, and see how it affects the program. Does it break? Did the output change? How did it change? Why did it fail?
Since starting from scratch is out of reach, the best middle ground is to work with pre-existing code. Try adding a feature not mentioned in the tutorial. This requires you to navigate the tutorial code and understand most of it to add something without breaking what is already there. And if you break something, it's not a big deal since you now have a self-inflicted coding challenge to solve.
When creating something from scratch, starting with a clear goal or problem to solve is helpful. For example, you could create a simple calculator or a program that generates random passwords; if you are more interested in game development, it could be as simple as making a square move right and left and nothing more. This will give you a framework and help you focus your efforts. But most importantly, it gives you an end goal. It allows you to finish something. This is great for your motivation to learn early in the learning stage and gives you a lot of momentum to go on to a new, slightly more demanding challenge.
As for resources, many online platforms offer exercises and challenges for beginners. Codecademy, Khan Academy, Codewars, and Udemy are all great places to start. Remember that learning to code is a process, and making mistakes and failing is okay. Keep practicing and asking questions, and you'll gradually develop the skills and knowledge you need to create projects from scratch.
P.S. Don't worry; your English skills are excellent, and you will only get better with time :)
does anyone else notice that this dude look like he's lip-syncing?
really liked the video!
Thank you so much for taking the time to watch my video and leaving a comment! I'm glad to hear that you liked it. Your support means a lot to me.
thx bro ur respected
Nice video
Naaa.
thanks god, I cannot follow any tutorial. (kinda ADHD, or they are not answering my question)
brackeys
what the heck people i post this and like five minutes later i get a love from the channel and a r adnom person o-O
Talk a bit louder😂
i will win
Eh I want to say as a educator this is terrible advice especially within in the creative field that is game development. But alas this is youtube anyone with a platform can give their advice an opinion and you don't need a degree and multiple years of education to teach people.
Some make some valid points but hammer on some pretty damaging things such as teaching people that "copying" is bad. It isn't. It's how we as humans learn from the get go. It is not a bad thing to copy. Also just because someone is copying doesn't mean they aren't actively learning and understanding. There are plenty of tutorials which teach people poorly and simply don't explain the reasons for what certain things are done and they simply create something not with the intent to teach their audience but to gain a viewership, get content out and continute their grind.
much information on the internet is unstructured in terms of learning.
adding to that is the conflict of interest between video lesson structure and monetization.
very few viewers actually have the time to sit down and watch an hour long lesson while taking notes, pausing the video to solve the questions by themselves, etc.
this means the real money is in entertainment, not in producing useful learning content.
I think the main thing he missed out is everyone learns differently, a tutorial can be great for people who learn from watching, but some people are more practical.
“I’ve been using unity since I was twelve” isn’t as impressive when you barely look 15.