Learn game dev by building your own games: https://www.skool.com/godot-mastery-2721/about

"Wait... Its all detections?"
"It always has been."

Being a game dev means being good with ducttape

While working on my own game project, I eventually created an object I call "GRIT":
Generic
Reusable
Interactable
Thing

The moment of realization genuinely made me feel like a Wizard learning magic when it happened to me

Detection is Collision. Transformation is Animation. Communication is Interaction. State & Logic is Memory.

Always remember that what you see in tutorials is the end product, so when someone in a tutorial makes a system in a 20-minute video, it doesn't mean that that person took just 20 minutes to make the system, he probably spend a MUCH bigger amount of time fixing bugs and improving the system and optimizing it, and then he make a quick video about the END product that doesn't include the process of bug fixing and designing. So don't feel too hard on yourself if you take a lot of time to make a mechanic.

Bold of u to assume the game works 00:27

The ultimate game dev tutorial

This is one of the most valuable programming videos I have ever seen on YouTube.

I'm a new gamedev but i had months of DSA and C++ experience before joining so it was easy for me to pick up through tutorials, it's nice to see that someone is teaching what I call "learning how to learn programming" instead of "learning programming." I'll share it with my brother to teach him this :D

This tutorial is more spiritual and philosophical than it seems.

Nice video! Breaking mechanics into their simplest possible step is always a great idea (helps me a lot when planning too!)

Hold your breath when you start the game, start breathing again when the gameplay starts. This will make you aware of where the seconds go.

Your video is a MUST for anyone wanting to code a game or anything, really. I'm an old school programmer, not even the WWW existed (for real) and we had to code, unaided.

What you convey here is key. Realize about the patterns. Isolate the commonalities. Solve those. Everything else is a matter of transforming details.

Great job, newcomers really need more material like this.

This is really helpful to see broken down. I think I had an idea that something like this might be the case, where things need to be broken down to better understand them, but not knowing much about programming I didn't quite know how to break them down, but I can already see/remember all of these types of things in recent AAA games I've played. Neat and thank you.

This is cute. I've been coding for decades and forgot that "ah ha" moment

The tutorial -> failed attempt -> tutorial -> give up pattern was me years ago. Even though I knew how to code from my data science job, gamedev had a lot of other required knowledge that I just didn't have.

Legendary Game Dev Tutorial

Finally, something actually worth understanding! After going through a nightmare of tutorials that gave me absolutely nothing, this is a lifesaver.