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.
On Day 42 of my game development journey, I reflected on roles, identity, and direction in game development.
What I tried / learned today
I learned that I don’t have to choose one role too early.
Right now, I feel like:
- 60% game developer
- 40% game designer
I’m putting 100% effort into game development, but I haven’t stopped learning design.
I learned that both roles are deeply connected.
Especially for indie developers, it’s normal to handle both design and development.
Learning both gives me:
- More control over my ideas
- A better understanding of how games actually work
What confused me
I was confused about:
- What to call myself
- Whether focusing on one path was mandatory
- People constantly saying “this is better than that”
I also wondered if learning both roles was a waste of time.
What worked or finally clicked
What finally clicked was simple:
Experience should come before decisions.
I realized:
- Only I can decide what suits me
- Listening blindly to others creates confusion
- Indie games usually need both skill sets
Before becoming indie, I also understood that I need a job first — and skills matter more than labels.
There’s a proverb that fits perfectly here:
“Don’t judge the path before you walk it.”
One lesson for beginners
- Don’t rush to label yourself
- Developer = technical side
- Designer = gameplay and ideas
- Learning both gives flexibility
- Career clarity comes with time
Slow progress — 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 🎮🚀
Top comments (0)