// Deciding as a parent
Is coding good for my child? An honest answer from two engineers
When coding helps a 10 to 16 year old and when it does not, what age to start, screen time answered plainly, and the questions to ask any provider first.
Coding is good for your child in some circumstances and not in others. The honest version of that answer is less marketable, so you don't often hear it. This guide is our attempt to give it to you plainly.
We're Ismail and Sami, engineers at AWS. We built Builders Club because we couldn't find a programme for 10 to 16 year olds that went past beginner Python and reflected how engineers actually work. We're not going to tell you coding is for every child, because it isn't.
In this guide we cover when coding genuinely helps and when it probably doesn't, what a child can realistically do at each age, how to think honestly about screen time, and the questions to ask any provider before you pay.
When coding helps a child
Coding helps a child who is curious about how things work rather than just how to use them. A child who wonders how a game decides what to do, or why a website looks different on a phone, is already asking the kind of question that leads somewhere. That curiosity doesn't require any prior knowledge of computers.
The feedback loop in coding is honest in a way that essays and tests often are not. You write something, it either works or it doesn't. Children who find it hard to stay motivated through abstract learning often find that building something concrete changes things.
The skills that carry across to other areas come from actually building things, not from watching videos about building things. That means real sessions with real code, where the child makes the decisions and reads the errors. Reading errors carefully and breaking a problem into smaller steps are things you can only learn by doing them.
When coding probably isn't worth it
Coding is not worth it if your child doesn't want to be there. A programme marketed at parents rather than children tends to produce children who sit through sessions without engaging. The free first session exists so you can find this out before you pay anything.
It's also not worth it if the programme stays at block coding for years. Block-based tools have their place at 7 or 8, but a child who is 10 and still moving coloured blocks around a screen is not learning how computers work. Typed code from the first session is what makes the concepts stick at this age.
If your child already codes seriously on their own, they probably don't need a Foundations-level programme. The free session will place them accurately, and you can start at the right level rather than the beginning.
What your child can realistically do at each age
At 10 to 12, keep typed code under 15 lines per session, with autocomplete and templates doing the rest. The concepts are real: conditions, loops, training a model, and calling an API. But the typing stays low so frustration doesn't overtake the thinking. These volume gates come from the England programmes of study, the AI literacy frameworks, and our own curriculum design, documented in our course overview.
At 12 to 14, typed code grows to under 40 lines, always from a template. Python that reads a file, calls an AI, or manages a conversation in memory. Real tasks with real errors to fix.
At 14 to 16, small programs built template-first, using AWS services in a sandbox we own and an AI that answers questions from their own notes. The jump between each stage is a year of building rather than a birthday.
12 and 14 year olds sit across two levels, so we place by experience rather than age alone. The free session is where that placement happens.
Is this just more screen time?
It's 90 minutes in front of a laptop, once or twice a week. During that time your child is writing code, talking to the engineer teaching them, and putting something on the internet. That's different from 90 minutes of watching videos, but it is still screen time, and you should weigh it against everything else in your child's week.
The distinction that matters is whether the screen is active or passive. Writing code is active: the child makes decisions and sees their effects immediately. A bug doesn't wait to be discovered; it shows up the moment you run the program. That said, we'd be telling you what you want to hear if we said the screen doesn't matter. You know your child's schedule better than we do.
Every Saturday we send you an email with a screenshot of what they built that week and one question to ask at dinner. That conversation, where your child explains something to you, is often where the learning lands.
Questions to ask any provider before you pay
These questions will tell you most of what you need to know about any coding programme. They apply to us too.
Who teaches the sessions, by name? A programme run by one or two named engineers is different from one that cycles through contractors. Ask who will be in the room with your child, and whether they'll still be there in six months.
What is the group size, and what is the age range inside the group? A group of 6 to 8 children at the same level is different from 12 children spanning four years in age.
What accounts will your child hold, and in whose name? Under 13, your child should hold no accounts in their own name: no coding platforms, no AI tools, no email addresses set up for them, and no cloud accounts in their name. Vague answers here are themselves an answer.
What happens when something goes wrong, beyond technical problems? What if your child is struggling, what if they want to leave, what if there's a difficulty with another child in the group, and what if the tutor changes?
How do you see progress? Ask what you'll receive, how often, and whether it shows you what your child built or only how many sessions they attended.
What Builders Club does
Live online sessions run by engineers who work at AWS. Groups of 6 to 8, once or twice a week, 90 minutes a session. The first session is free and places your child accurately before you pay anything.
No accounts in your child's name under 13. Everything runs in the browser on platforms we manage. From 13, your child creates a GitHub account in a session with you present. We own everything else, the Linux server, the AI tools, the AWS sandbox, and anything else the programme runs on. We pay the bills.
Every module closes with a project your child demos to you at a Parent Showcase. The Saturday email tells you what they built each week and gives you one question to ask them about it.