Every week a parent writes to say "my child is addicted to games, I want them to learn coding so they stop playing". Let me be honest: coding is not a cure for gaming. But it is a bridge that genuinely works for one group of children.
Two very different kinds of gamer
The first plays to feel skilled. They care about rank and about winning. Coding rarely holds them, because it delivers that feeling of mastery far more slowly than a game does.
The second plays because they want to know how it works. They explore maps, poke at bugs, watch videos explaining game mechanics. These children really do become makers, often surprisingly quickly.
How to tell which you have
Ask one question: "If you had designed this game, what would you change?"
- "I dunno, it is fine" — not the moment yet.
- A minute-long answer about a character being overpowered and what level three needs — that is a maker who does not know it yet.
Opening the conversation without a fight
The least effective opening is "stop playing and go learn programming", because what the child hears is that the thing they love is worthless.
What works is raising the thing they already love: "how do you think the people who made this built it?" or "if you made your own game, what would it be?"
The goal is not that they stop playing. It is that they learn they can choose which side of the screen to be on.
Show them something real, fast
Children believe what they see far more than what they are told. That is why our students design a game and have it published and playable on the web straight away, with a link they can send to friends.
Open our students' games page with your child and mention that one of the makers is six years old. Their reaction will answer the question for you.
And if it does not work?
That is fine too. A child who tries and discovers it is not for them still keeps the step-by-step thinking, and has learned something true about themselves years earlier than they otherwise would.
