Why Age Is the Wrong Metric
When parents call us to enquire about enrollment, one of the first questions is almost always: "Is my child old enough?" It's a natural question, but it's asking the wrong thing. Age is a rough proxy for readiness, and for coding it's a particularly unreliable one.
We have enrolled six-year-olds who took to Scratch like fish to water, completing multi-sprite projects by their fourth session. We have also worked with eleven-year-olds who needed several more months before the logical thinking clicked. What made the difference had nothing to do with their birthday — it had everything to do with five specific curiosity and behaviour patterns.
The right question isn't "Is my 7-year-old old enough to code?" It's "Does my child show the signs that make coding a natural next step?" Here are the five we look for.
Sign #1 — They Ask "How Does That Work?"
Children who are naturally curious about mechanisms — how toys work, how apps know their name, how the traffic light knows when to change, how Siri understands speech — are wired for programming thinking. Coding is fundamentally about understanding and building systems. The child who wants to know why and how, rather than just accepting that something works, already has the most important cognitive habit a programmer needs.
You don't need to know how to answer their questions. The curiosity itself is the signal. If your child regularly asks about the inner workings of things — digital or physical — that instinct transfers directly to the debugger's mindset: "something's happening here, I want to understand it."
Sign #2 — They Love Building and Creating
Lego towers, Minecraft worlds, elaborate drawings, games they invented with their own rules, craft projects that sprawl across the kitchen table — all of these are proto-coding activities. The impulse to create structured systems from raw materials is the same impulse that drives great software development.
What we're looking for isn't any specific hobby. It's the orientation toward making things rather than just using them. A child who spends 45 minutes carefully constructing something (even if it collapses at the end) is practicing exactly the persistence and creative problem-solving that coding demands.
Sign #3 — They Can Follow Multi-Step Instructions
A child ready for coding can follow a recipe, assemble a kit from a manual, or play a board game with multiple rules without getting lost. This sequential thinking — do A, then check if B, then do C or D depending on the result — is the foundation of algorithmic reasoning. It's the mental model that programs run on.
This doesn't mean your child needs to be perfectly patient or never make mistakes. It means they understand that the order of steps matters, and that they can hold a multi-step process in mind without losing the thread. If your child can navigate a board game, they can navigate a Scratch project.
Sign #4 — They Enjoy Puzzles and Problem Solving
Puzzle lovers, mystery readers, children who get absorbed in logic games — kids who derive genuine satisfaction from solving structured problems take to coding quickly. Debugging a program is a puzzle: something isn't doing what it should, there are clues in the code, and the solution requires systematic thinking and a willingness to test hypotheses.
The joy of the "aha moment" — when the pieces suddenly click into place — is the same whether you're solving a jigsaw or fixing a broken loop. Children who love that feeling are natural coders.
Sign #5 — They're Comfortable With Not Getting It Right Immediately
This is the most important sign of all. Coding involves failure — every single session. Programs don't work the first time. Errors happen constantly. The question is whether a child can treat those failures as information rather than defeat.
Children who get frustrated and give up at the first error struggle more than children who are naturally persistent — but here's the crucial nuance: this is also something that good teaching actively develops. We have helped many children build this resilience who didn't naturally have it. A short attention span doesn't disqualify a child. It just means the early sessions need more scaffolding and encouragement.
Questions to Ask Your Child Before Enrolling
- "What do you think is inside a computer?"
- "If you could make any game, what would it be?"
- "How do you think Siri or Alexa understands you?"
- "What would you build if you knew how?"
- "Have you ever wanted to make your own app or game?"
What If My Child Doesn't Show All 5 Signs?
You don't need all five. Two or three is more than enough. In our experience, curiosity plus a willingness to try again is the magic combination — everything else is buildable from there. The love of building, the ability to follow multi-step instructions, the puzzle-solving instinct — all of these grow through good instruction and a supportive environment.
The children we worry about are those who show genuine disinterest in technology and strong aversion to challenge — but even then, the right project at the right moment can change everything. If your child is curious about anything at all, there's almost certainly a coding project that connects to that curiosity. That's exactly where we start.