How We Check a Child Can Code Without Help

Michael Murr··6 min read

Last updated: November 2026

If you have paid for coding lessons and still could not say what your child can do on their own, you are asking the question most lessons never answer. Here is how we answer it, starting with the moment that showed me why "yes, I understand" is not an answer.

In August I reviewed three back-to-back Scratch lessons with one of our youngest beginners. One idea kept coming back: the coordinate grid, the x and y numbers that decide where a character sits on the screen.

At the start of the second lesson, the instructor asked whether the child knew what x and y meant. The honest answer was no. Nothing from the week before had survived. So it was taught again, properly this time, and at the end of that lesson the child explained both axes correctly, in their own words.

By any normal standard, that is a lesson that worked.

In the third lesson, the child described the axes backwards. Later in the same hour, they asked what one of the terms even meant.

The child was sure, and the child was wrong

Nobody failed in that story. The second explanation was good, and the child really did have it at the end of that hour. What the check measured was the hour, not the skill.

The part that matters for you as a parent is the confidence. In the third lesson the child did not feel lost. They felt sure, and they were wrong. That is the normal state of a beginner. They do not know what they do not know, so "did you understand?" gets a yes every time.

Psychologists David Dunning and Justin Kruger studied a version of this in 1999: people with low ability in an area tend to give overly positive assessments of their own ability. In a coding lesson, that makes a beginner's own sense of "I've got it" the least reliable signal in the room.

So we do not ask. We watch.

Every lesson runs the same way. The instructor explains a concept, shows an example, and answers the child's questions, with both screens shared. Then, before anything new, comes the challenge: a small problem the child solves alone while the instructor watches. No example to copy, no hints, no AI tool doing it for them.

Getting it wrong is fine. Getting it wrong is the point, because a wrong answer shows exactly where the gap is while it is still small. One parent's review put the effect better than I can:

"I loved the challenges. They really helped my learning. Completing challenges on my own was very motivating. Exactly what I needed." Michelle, parent of a daughter learning Python

What a wrong answer tells us

In Python, the challenges surface the same kinds of slip again and again: a missing colon at the end of an if or for line, or a loop whose condition was forgotten. The colon is not decoration. Python's language reference says every clause header "ends with a colon," so one missing character stops the whole program.

A child who drops the colon once is learning. A child who drops it in three challenges running has a pattern, and now the instructor knows exactly where to slow down.

The challenges show the opposite too. Some concepts come fast, and the lesson speeds up. Others need another example before anything gets built on top of them. The pace is set by what the child did alone, not by a syllabus.

The checks grow with the course. At the end of each section there are short puzzles the child does alone between sessions, with the instructor reachable for questions. From the functions section onward, the challenges stop being stand-alone exercises and become parts of a larger project the child builds across the section. By then the question is no longer "can you solve this small problem?" It is "can you build the next piece of your own program?" That is much closer to what you actually want to know.

Back to the coordinate grid. Across those three hours, the evidence sorted what that child knew into two piles. Solid: starting a program, loops that repeat or run forever, costumes, choosing between two paths when a key is pressed, and clones. Not solid yet: the x and y axes, using a character's position as a number you can test, and comparison operators.

That second pile is the useful one. It is a list of exactly what the next lessons have to come back to, and no amount of asking "how was your lesson?" would have produced it.

It is also why a check at the end of a lesson is never the last word. The next lesson should open by asking the child to recall the idea before anything new goes on top of it. If it is still there, you move on. Finding out costs thirty seconds. Rebuilding it from zero costs fifteen minutes. I wrote up the full story, and the one-page reference that fixes most of it, in why your child forgets last week's coding lesson.

What I tell every parent now

We do not grade children and we do not rank them. A score would tell you less than this does. What we do is make sure that every lesson contains a moment where your child works with nobody helping, and someone who knows what to look for is watching.

When the challenge breaks, the instructor does not fix it. They ask what the child expected and what actually happened, then wait. That restraint is a skill in itself, and I have written about teaching kids to debug without fixing it for them. The milestone all of this builds toward is a child opening a blank file and producing something that runs, badly, entirely on their own. The first time a student writes code from scratch is what that looks like when it happens.

What the challenges show is the evidence behind the progress reports you receive: what your child did alone, where they slipped, and what comes next. Here is what a progress report contains.

Asking a child whether they understood tells you how they feel. Watching them do it alone tells you what they can do. If you have never seen your child code with nobody helping, that is the first thing worth finding out, and a free Discovery Call is where we start.

Frequently Asked Questions

Do you give children tests or grades? No graded tests and no rankings. Instead, every new concept ends with a small challenge your child solves alone while the instructor watches, and each section ends with short puzzles done alone. It is a check, not a score.

What if my child gets the challenge wrong? That is fine, and often more useful than getting it right. A wrong answer shows exactly which step is missing, so the next example can target it. A challenge that never goes wrong is usually too easy to tell you anything.

How will I know what the challenges showed? Through the progress reports, which describe what your child understood and where they struggled. The challenges are where that evidence comes from. See what a progress report contains.

Keep reading

More guides for parents on the same topics.

Enjoyed this article?

Your child can learn this and more with a dedicated 1-on-1 tutor.

Book a Free Discovery Call