How long does it take for a child to really learn to code?

"How long until my child really knows how to program?" It's a question we hear almost as often as the one about starting age, and it comes from a flawed assumption: that "knowing how to code" is a threshold you cross one day, like learning to swim. In reality it's a continuous progression, with very concrete milestones at each stage — here's what they look like.

After a few sessions: the first blocks come to life

By the first or second session, a child can already make a character move, react to a key press, build a simple loop. It's not "programming" in the adult sense yet, but it's already the right logic: giving precise instructions to a machine and observing the result. This is the stage where the magic happens — seeing their own program react, for the first time.

After about 3 months: a first real project, start to finish

This is usually when a child finishes their first complete project mostly on their own: a mini-game with several levels, an interactive quiz, an animation with multiple characters interacting. They start anticipating problems before they happen ("if I don't add a condition here, it'll break"), a sign that logic is settling in, not just block memorization. That's also, concretely, the length of a first commitment with us — not a coincidence: it's usually how long it takes to complete a full learning cycle, from discovery to a result worth showing.

After 6 to 12 months: the transition to a real text-based language

This is the period when, for most children, Scratch starts showing its limits and the transition to Python (often via Python Turtle first) becomes natural. The child writes their first lines of text-based code, with real syntax — a symbolically important step, even though the underlying concepts remain largely the same as in Scratch. See Scratch vs Python, what's the difference to understand why this transition is a change in representation, not in level.

Beyond a year: growing independence

At this stage, a child can generally start from a personal project idea ("I want to make a game where...") and build it with less and less help, debugging their own mistakes before asking for assistance. This is also when some start getting curious about broader topics: how a website works, artificial intelligence, databases.

What actually speeds progress up — and what slows it down

Three factors make a real difference, in order of importance. First, consistency (more on that below) — nothing offsets a course interrupted for months. Second, free practice between sessions — even 15 spontaneous minutes tweaking their own project is often worth more than an extra supervised hour, because the child is solving their own problems, on their own initiative. Third, having a real personal project in progress rather than a string of disconnected exercises: a child who wants to finish "their" game pushes through obstacles with far more persistence than for an assigned exercise. On the other hand, what slows progress down most often: long breaks (a summer month with zero practice genuinely erodes some of the reflexes built up), and sessions spaced too far apart from the start, which never lets momentum build.

Intensive camp or regular class: which progresses faster?

The two formats don't answer the same question. A holiday camp packs 12 hours into one week — enough to finish a complete project and feel real, fast progress, but some of that effect fades without follow-up. A regular class moves more slowly week to week, but consolidates over time thanks to the natural spacing between sessions. In practice, the most effective combination we see is a camp to kick things off or for an occasional boost, paired with regular follow-up so none of it erodes between camps.

Why consistency matters more than intensity

One hour a week for 6 months produces better results than six hours in a row over a single weekend. The brain needs time between sessions to consolidate what was just learned — true for coding as much as for a language or a musical instrument. That's why our plans are built around 3, 6 or 12-month commitments rather than single sessions: consistency is part of the result, not just the total hours logged.

Frequently asked questions

My child has been stuck for a few weeks, is that normal? Yes, and it's actually expected: progress is never perfectly linear. A plateau of a few weeks often comes right before a real jump, while concepts connect with each other. It's the teacher's job to tell a normal plateau apart from a genuine block that needs a different approach.

Can you "catch up" after several months off fairly quickly? Partly. Concepts usually come back fast (a few sessions), but problem-solving reflexes take a bit longer to settle back in than they took to fade.

Do two children who start at the same time progress at the same pace? Rarely exactly, even between siblings of the same age — which is precisely why our classes stay one-on-one or in very small groups rather than following a shared curriculum.

Not sure yet what pace would suit your child? The free trial lesson (30 minutes) lets you start without any commitment, and our holiday camps offer an intensive one-week preview before deciding on regular sessions.