How to Inspect Your Kid's Work When You Are Not Technical

Your kid is building something technical, and you cannot evaluate the technical part because it is not your field. So you are left trusting that learning is happening, or quietly worrying that it is not, with no way to check. This is one of the most common anxieties among parents of kids in any technical pursuit, and it rests on a false assumption: that you need to understand the subject to tell whether your kid is genuinely learning it. You do not. The signals that matter are not technical at all.

What you are actually checking for is understanding, ownership, and honesty, and all three are visible to anyone, in plain conversation. Here are the questions that reveal them, and why they work no matter how non-technical you are.

Why you do not need to understand the subject

The instinct is that judging your kid's coding, or any technical work, requires understanding the code. But that is judging the artifact, and you do not need to judge the artifact. You need to judge the learner. And the marks of a real learner, do they understand what they made, did they actually make it, can they see its flaws honestly, show up in how a kid talks about their work, not in the work itself. A person who genuinely understands something can explain it simply, account for their choices, and critique it honestly, regardless of the subject. Those are the things you are checking, and they are perfectly visible to you.

You are not grading the code. You are reading the kid. Whether a kid understands their work, owns it, and can see its flaws shows up in plain conversation, and you are fully equipped to hear it.

The questions that reveal understanding

The single best test of understanding is the ability to explain something simply to someone who does not know it. Use yourself as that person, honestly.

• "Explain what this does like I have never seen it." A kid who understands their work can put it in plain language a non-expert follows. A kid who is parroting or faking gets vague, jargon-heavy, or circular, because you cannot simplify what you do not understand. Listen for whether the explanation actually lands for you. If it does, they get it.
• "Why did you do it this way and not another way?" Real understanding shows up as reasons. A kid who made genuine choices can tell you why they chose what they chose. A kid who copied without understanding cannot explain the why, because there was no decision, just imitation.
• "What part was hardest, and how did you get past it?" A kid who did the work has a real story of a specific struggle and how they solved it. A kid who did not has nothing concrete to say, because they were not there for the hard parts.

Notice that none of these requires you to understand the answer's technical content. You are listening for clarity, reasons, and specificity, which you can absolutely hear.

The question that cuts through everything

When in doubt, fall back on the most powerful and least technical request of all: "Show me it working." Not the plan, not the code, not a description, the actual thing, running, doing what it is supposed to do. This single move cuts through nearly everything, because a working thing is undeniable and a described thing is not.

A kid who can show you something real, even rough and unfinished, that actually does something, is genuinely building. A kid who can only describe what it will do, or shows you something that does not quite work and talks around it, is somewhere earlier or stuck, which is useful to know. You do not need to understand how it works to see that it works. Reality is legible to everyone, and "show me it working" makes a kid put reality on the table.

The question that tests honesty and judgment

The deepest check is about whether your kid can judge their own work, which is the whole skill in miniature. Ask: "What is wrong with it, and what would you fix next?"

A kid who is really learning can tell you, readily, what is not good about their own thing and what they would improve. That honest self-assessment is the mark of a genuine builder, because the ability to see your own work clearly is exactly what separates someone who is learning from someone who is performing. A kid who insists it is all perfect, or cannot name a single flaw, either does not understand it well enough to see the flaws, or is not being honest, and both are worth knowing. The kid you want is the one who can cheerfully list three things wrong with their own creation and what they would do about them. That kid is learning the most important thing of all.

The free Parent Field Guide below is written in the same spirit, plain language for non-technical parents, and it covers how to help your kid start something real worth inspecting. It is useful on its own, with nothing to buy.

The honest bottom line

You do not need to be technical to know whether your kid is really learning, because the things that matter, understanding, ownership, and honesty, are not technical and show up in plain conversation. Ask them to explain it like you have never seen it, to tell you why they made their choices, and what was hardest. Ask them to show you it working, which is the great equalizer. And ask what is wrong with it and what they would fix, which tests the honest self-judgment that is the heart of real learning. Ask all of it warmly, curious rather than testing. You are fully equipped to read your kid, even when you cannot read the code.