I Stopped Labeling Myself Too Early in Game Development
Source: Dev.to
Introduction
Everyone kept asking what I am — designer or developer. I didn’t have a clear answer, and I finally realized that’s okay.
This post is part of my daily learning journey in game development. I’m sharing what I learn each day — the basics, the confusion, and the real progress — from the perspective of a beginner.
Day 42: Roles, Identity, and Direction
I reflected on roles, identity, and direction in game development and learned that I don’t have to choose one role too early.
Current Focus
- 60 % game developer
- 40 % game designer
I’m putting 100 % effort into game development, but I haven’t stopped learning design. Both roles are deeply connected, especially for indie developers who often handle both design and development.
Benefits of Learning Both
- More control over my ideas
- A better understanding of how games actually work
What Confused Me
Questions I Had
- What should I call myself?
- Is focusing on one path mandatory?
- Why do people constantly say “this is better than that”?
I also wondered if learning both roles was a waste of time.
What Finally Clicked
Experience should come before decisions.
Realizations
- Only I can decide what suits me.
- Listening blindly to others creates confusion.
- Indie games usually need both skill sets.
Before becoming indie, I understood that I need a job first — and skills matter more than labels. A proverb that fits perfectly here:
“Don’t judge the path before you walk it.”
Takeaways
- Don’t rush to label yourself.
- Developer = technical side
- Designer = gameplay and ideas
- Learning both gives flexibility.
- Career clarity comes with time.
Conclusion
Progress is slow, but I’m building a strong foundation. If you’re also learning game development, what was the first thing that confused you when you started?
See you in the next post 🎮🚀