There’s a $4.67 billion industry that would like you to believe the right toy will give your kid a head start in tech. The packaging says “coding.” The app says “STEM.” The price tag says this one is worth it.
I spent twelve years writing software before I left a director-level job and stayed home. I’ve seen what actually makes an engineer good at reasoning, and it has nothing to do with the toy they had at four. It comes down to whether someone taught them to break a problem apart, handed them something that didn’t work, and stuck around while they figured out why.
No toy does that. You do.
What the research is actually finding
In March 2026, Lancaster University and the Micro:bit Foundation launched the Micro:bit Innovation and Research Lab (MIRL) , a formal effort to scale hands-on computing education with evidence behind it. The micro:bit program has already put 11 million devices into 85 countries, reaching over 70 million children. The telling part is that they built a research lab instead of just shipping more units – because handing out devices and building thinkers turn out to be two different things.
The IDC 2025 study on Bit:sort – a physical sorting activity for fourth graders – found something that should reframe how you think about early computing entirely. Kids demonstrated genuine algorithmic reasoning through physical play even when they couldn’t put it into words. They were thinking in algorithms before they had the language for it, and the reasoning grew out of doing rather than being told.
The TMAR study pushed further. When students were asked to invent their own challenges instead of completing preset ones, they showed significantly stronger gains in abstraction, decomposition, and algorithmic reasoning – the three pillars of computational thinking. Student-generated problems beat instructor-assigned ones on every metric that mattered.
The kids who made the problems got smarter than the kids who solved them.

Why this matters if your kid is under six
The STEM toy market has a well-known gap for ages two to three. Most products aim either at babies (sensory, no logic) or at school-age kids (screen-based, app-dependent, increasingly passive). The shift researchers and educators are now watching – away from app-dependent toys and toward open-ended, screen-free, reusable play – is a direct response to evidence that passive engagement doesn’t build reasoning.
For a three-year-old, the foundational moves have nothing to do with a particular device. They’re about learning to notice patterns, test a hypothesis, hit a dead end, and try again. That loop is the whole thing. The physical substrate – blocks, magnet tiles, a simple circuit, a game you build together – matters far less than whether the child is the one deciding what happens next.
An AI toy that responds to your child is a very different thing from a problem that doesn’t respond at all until they figure it out. Only one of those leaves the thinking to the kid.

The build-together advantage
Here’s what changes when you sit down and make something with your kid instead of setting them up with something that was made for them.
First, you narrate your own thinking out loud. “Hmm, this isn’t doing what I expected – why might that be?” Your child learns that uncertainty isn’t a failure state, just the next step in the work.
Second, the challenge is theirs to define. The TMAR research is clear that self-generated challenges beat preset ones. When your kid says “I want to make a game where the cars race and crash into each other,” that’s not just chaos – it’s the child setting the parameters, and your job is to help them build toward it.
Third, you can’t be replaced by an app, because the relationship is the scaffold. Research on early learning consistently shows that co-regulation – a calm adult presence modulating a child’s frustration – is what lets children stay with hard problems long enough to solve them. A toy can’t co-regulate. You can.
An AI toy won’t sit with your kid through the seventh dead end and keep its voice level while asking what they want to try differently. Toys are built to respond in a believable way, not to teach. The gap there isn’t a missing feature you can patch in a software update – it’s the difference between a convincing performance and an actual teacher.
What this looks like in practice
If you want a structured starting point for building with a child under six, I wrote a twelve-week project curriculum – physical and digital projects for the pre-reader age range, built around the exact principles the research supports: child-directed challenges, hands-on iteration, parent presence as the scaffold. It’s practical and week-by-week, not theoretical.
The projects don’t require any prior programming knowledge. What they require is your time and your willingness to be genuinely curious right alongside your kid.
You were already the advantage. You just needed the roadmap.
