You Will NEVER Become a Game Dev by Using Unity Tutorials

In this video, I discuss why relying solely on Unity tutorials may not make you a successful game developer. We'll be diving into the essential skills and knowledge needed beyond Unity tutorials to help you reach your goal of becoming a game dev.

#gamedev #unitydev #unitytutorial

[necrow]

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.

[sirgregoryadams]

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

[caeleng]

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!

[envernigmatouline]

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.

[Zhurak]

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!

[Amricium]

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?

[otamatonegaming]

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

[mrtutorials]

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

[d_ne]

Very high quality video, I didn't even notice I wasnt watching some 200k subs channel. Keep up the good work👌

[JordonRenn]

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.

[markguyton]

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.

[Somali_Salamander]

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.

[Mrminico]

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.

[elijah-jones-inbox]

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.

[DRATER]

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.

[simplyVIRTUL]

so that means that i gotta learn scripting language by myself with no help? nah bro, you're trippin

[code-knight]

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.

[enzozaqueu]

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

[jannyboi]

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.

[gamnrd]

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