My son is obsessed with garbage trucks.
Not casually interested. Obsessed. He knows our neighborhood’s pickup schedule. He can identify the squeal of the brakes from half a block away.
Every garbage day, we stood out on the sidewalk and watched the truck the way other families watch fireworks.
So when I wanted to introduce him to computational thinking – to start laying the foundation for building things together – I had a choice. I could follow a curriculum: “Week 1: colors. Week 2: shapes. Week 3: sequences.” Or I could follow the garbage trucks.
I followed the garbage trucks, and I haven’t looked back.
The Curriculum Trap
There’s a whole industry of “teach your kid to code” products, and most of them are built the same way: a fixed sequence of lessons marching through concepts in a tidy order. First you learn this, then that, then you combine them.
On paper it makes sense. It’s how we organize a computer science degree – prerequisites first, advanced topics later, building blocks stacked in order.
The trouble is that toddlers do not care about your tidy order. They care about what they care about, and what they care about changes by the hour. But in any given hour, the interest is intense.
When my son cares about garbage trucks, he’ll stay locked onto garbage-truck activities for an astonishing stretch of time. Thirty minutes. Forty-five. That’s a geological age in toddler time. He’s asking questions, making connections, holding onto information.
When he doesn’t care about something, I get maybe thirty seconds before he’s upside down on the couch asking for a snack.
So why fight it? Why work so hard to make him care about abstract shapes on a screen when he already cares – deeply, fiercely, with his whole body – about garbage trucks?
Interest as an Engine
Here’s what it looks like in practice.
The concept I want to teach: sequencing (step-by-step instructions).
The curriculum version: “Let’s learn about sequences! Here’s a cute robot. Drag the arrows to make it walk to the star.”
The interest-led version: “What does the garbage truck do first when it gets to our house? Then what? Then what? Can we make a garbage truck game that does all those steps?”
Same concept. The difference in engagement is night and day.
In the interest-led version, my son was practically vibrating. He rattled off the truck’s entire pickup routine from memory – pulls up, extends the arm, grabs the can, lifts, dumps, lowers, releases, drives to the next house. That’s an eight-step algorithm, and he generated every step of it himself, because it was about something he loved.
A curriculum hands the kid a problem someone else defined. Interest-led learning lets the kid define the problem. The second one wins, and it isn’t close.
But What About Coverage?
This is the question I always get from other developer parents, because we’re wired to think in terms of completeness. “If you just follow interests, won’t there be gaps? What about concepts they never happen to bump into?”
What I’ve found is that with a little creativity, you can teach almost any foundational concept through almost any interest. The one prerequisite is knowing the concepts well enough yourself to spot the opening when it comes.
Garbage trucks alone can teach:
- Sequencing: the pickup routine
- Conditionals: “What if the can is too heavy? What if it’s recycling day?”
- Loops: “The truck does the same thing at every house on the street”
- Debugging: “What if the arm misses the can?”
- Pattern recognition: “Which streets does the truck visit on which days?”
- Decomposition: breaking the full route down into individual stops
That’s a whole introductory algorithmic-thinking curriculum, delivered through one obsession.
And the gaps? They fill in on their own, because kids’ interests move. Garbage trucks this month, airplanes next, space the month after. Each new obsession is a fresh vehicle (pun fully intended) for the same underlying concepts, met again in a different context.
That turns out to beat a curriculum, which teaches each concept once and moves on. Interest-led learning circles back to the core ideas over and over, in varied settings – which is how durable learning actually forms.
The Developer Analogy
Think about how you learn best as a developer.
Ever tried to learn a new framework by reading the docs cover to cover? How did that go? You probably retained about 15% and forgot most of it before you needed it.
Now think about a framework you learned because a project you cared about required it. You had a problem, the framework solved it, and you picked up exactly what you needed as you went. You retained far more, and the whole thing was faster and more enjoyable.
That’s interest-led learning, and it’s how adults learn best too. The only real difference is that an adult can occasionally force themselves to grind through boring material. A kid can’t. And honestly, why should they?
How to Do It
If you want to try interest-led tech learning with your kid, here’s the practical version.
1. Find the current obsession. What does your kid talk about nonstop? What would they do all day if you let them? That’s your vehicle.
2. Map concepts onto the interest. Take the computational thinking concepts you want to introduce – sequencing, patterns, conditionals, decomposition, debugging – and work out how each one connects to the obsession. I promise it does.
3. Let the kid drive. Don’t announce “let’s learn about patterns using trucks.” Say “hey, the garbage truck always goes to the same houses. Does it go in the same order? Why?” Let the concept surface out of the conversation.
4. Build something. This is where it gets powerful. “Want to make a garbage truck game?” takes the interest and adds creation. Now your kid isn’t just meeting concepts – they’re using them to build something they actually want to exist.
5. Follow tangents. If you’re building a garbage truck game and your kid suddenly wants a dinosaur riding on top, go with it. The tangent is just another interest surfacing, and the concepts still apply.
The Hard Part
I’ll be honest: interest-led is harder on the parent than curriculum-led, in some ways. A curriculum tells you what to do each day. Interest-led asks you to improvise – to find the computational thinking inside whatever your kid happens to be obsessed with this week, and to do it on your feet.
It’s also a lot more fun, because you’re responding to a real kid with real enthusiasm instead of marching through somebody else’s lesson plan. And the payoff is hard to argue with: deeper engagement, better retention, and a kid who connects learning with their favorite things rather than with obligation.
And if the only thing they keep from your “lessons” is a love of learning, that’s more than enough.