When I started learning game development, I constantly wondered where to start, how to start, and which tutorials were the best.
I searched YouTube for tutorials and even asked ChatGPT to recommend the best learning playlists.
But as I entered the actual development phase, I started facing a different problem.
I was watching tutorials, but I didn't really know what I was doing.
I learned C# for Unity, but when I started making games, I couldn't understand how to approach things the way developers in those tutorials were doing.
I kept wondering:
How do I start? How do I implement this? Why can't I do what I'm watching someone else do?
And eventually, I started questioning my own abilities.
But here's something I learned along the way:
You don't need to know everything before you start developing.
Sometimes, you just need to take a deep nap nap means Just breath a while and look back at what you've already learned.
Understand the concepts. Experiment with them. Try to implement them in different situations.
Imagine having a ball in your hand. You should have enough control over it that you can throw it in whichever direction you want.
That's how you should approach learning a different concept.
Don't just memorize it. Understand it well enough to use it wherever you need it.
Senior developers have experience, and there's a lot we can learn from them. Tutorials, documentation, AI, and experienced developers can all guide us.
But nobody can build that understanding for you.
You have to take ownership of your learning.
Don't consider yourself dumb just because you cannot implement something on your first attempt.
You're learning. Experiment, make mistakes, ask questions, and keep building.
Your goal isn't to become someone who can follow every tutorial.
Your goal is to become someone who can build something without needing one.
Top comments (0)