The Kit Arrived on a Tuesday

Forty-seven pieces of plastic, a cable that might have been a USB or might have been something else, and a manual that opened with the sentence: "Before you begin, ensure your firmware is updated."

My daughter looked at me. I looked at the manual. I said, "Right, let's start with the pieces."

That was the moment I understood what being a non-technical parent actually means in practice. Not that you can't help - you can. But the help looks different to what you expected.

What you don't need to know

You don't need to understand how circuits work or what a servo motor is. You don't need to have done any coding yourself. You don't need to know what firmware means (it's just the software inside the device - updating it usually means connecting to Wi-Fi and pressing one button, and the app will tell you when it's needed).

What you actually need is the ability to read an instruction diagram and match a picture. That's it. If you can assemble flat-pack furniture, you can do this.

The coding part - the bit that looks most intimidating - is usually drag-and-drop blocks on a tablet. Green block: move forward. Red block: stop. Your child will figure out the logic faster than you will, which is fine. That's the point.

What you are actually there for

Not to know the answers. To ask the questions.

When the robot doesn't do what it's supposed to do - and it won't, regularly, especially at first - the most useful thing you can say is not "let me look that up" but "what have you tried so far?" Then: "what do you think is causing it?" Then: "want to test that?"

This is not a trick. It's just that debugging a robot and debugging a problem are the same skill, and your child learns it by doing it, not by watching you do it. Your job is to keep them in the chair long enough to get there.

The evening my daughter's robot wouldn't turn on, I spent five minutes suggesting things - wrong cable, dead battery, loose connection - before she spotted the tiny power switch on the battery pack that we'd both missed entirely. She flicked it. The motor whirred. She did a lap of the kitchen.

I hadn't solved it. But I'd kept us both looking until she did.

The bits that are actually hard

The instructions are often written for someone who already knows what they're doing. When they're confusing - and they will be confusing - the move is to look at the picture, not read the text again more carefully. The picture is almost always clearer.

There will be an evening when neither of you wants to do this. A session that ends in frustration rather than a working robot. That's normal. Come back to it in a day or two, not an hour. Time away from a stuck problem is underrated.

Some children hit a wall around the third or fourth session when the novelty has worn off but the skill hasn't caught up yet. This is the hardest bit. The ones who push through it tend to get genuinely hooked. But pushing through it requires someone sitting nearby who isn't giving up either.

That's you. You don't have to understand the code. You just have to still be there.

What changes over time

The questions your child asks will outpace what you can answer. This happens sooner than you expect, and it's a good sign. When it does, "I don't know - how could we find out?" is the right response. Not because it's a teaching technique, but because it's true, and they'll respect the honesty.

After a few months, you'll notice something shift. They'll start explaining things to you - what the sensor does, why the loop matters, what they changed and why it worked this time. At that point, your job has mostly changed from guide to audience. That's a good place to be.

The only thing you actually need to bring to every session is this: a genuine willingness to not know, and to keep going anyway. Your child is watching that more than they're watching the screen.