Why “Interest-Led” Beats “Curriculum-Led” for Teaching Kids Tech
My son learned algorithmic thinking from garbage trucks. Your kid can learn it from whatever they're obsessed with right now.
My son is obsessed with garbage trucks.
Not casually interested. Obsessed. He knows the pickup schedule for our neighborhood. He can identify the squeal of its brakes from half a block away.
Every garbage day morning, we stood outside and watched the garbage truck like other families watch fireworks.
So when I wanted to introduce him to computational thinking — to start building the foundation for tech projects together — I had a choice. I could follow a curriculum: “Week 1: Learn about colors. Week 2: Learn about shapes. Week 3: Learn about sequences.”
Or I could follow the garbage trucks.
I followed the garbage trucks. And it changed everything.
The Curriculum Trap
There’s a whole industry of “teach kids to code” products, and most of them share the same structure: a predefined sequence of lessons that march through concepts in a logical order. First you learn this, then you learn that, then you combine them.
It makes sense on paper. It’s how we organize knowledge in computer science courses. Prerequisites before advanced topics. Building blocks stacked in order.
The problem is that toddlers and young kids don’t care about your logical order. They care about what they care about. And what they care about changes by the hour, but at any given moment, it’s intense.
When my son cares about garbage trucks, he will sustain attention on garbage truck-related activities for an astonishing amount of time. Thirty minutes. Forty-five minutes. That’s an eternity in toddler time. He’s asking questions, making connections, retaining information.
When he doesn’t care about something? You get maybe thirty seconds before he’s upside down on the couch asking for a snack.
So why would I fight that? Why would I try to make him care about abstract shapes on a screen when he already cares — deeply, passionately — about garbage trucks?
Interest as an Engine
Here’s what interest-led learning looks like in practice:
The concept I want to teach: Sequencing (step-by-step instructions)
Curriculum approach: “Let’s learn about sequences! Here’s a cute robot. Drag the arrows to make it walk to the star.”
Interest-led approach: “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. Wildly different engagement.
In the interest-led version, my son was practically vibrating with excitement. He described the garbage truck’s entire pickup sequence 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 it himself because it was about something he cared about.
In a curriculum, someone else defines the problem. In interest-led, the kid defines the problem. Guess which one produces better learning?
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 naturally encounter?”
Here’s what I’ve found: if you’re creative about it, you can teach almost any foundational concept through almost any interest. The only prerequisite is knowing them well-enough yourself to spot the opportunities.
Garbage trucks 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 go to on which days?”
Decomposition: Breaking down the full route into individual stops
That’s basically an entire basic algorithmic thinking curriculum, delivered through a single interest.
And here’s the thing about gaps: they fill naturally. Because kids’ interests change. Garbage trucks this month, airplanes next month, space the month after. Each new obsession is a new vehicle (pun intended) for the same underlying concepts, reinforced in a different context.
That’s actually better than a curriculum, which teaches each concept once and moves on. Interest-led learning revisits core concepts over and over, in varied contexts, which is how durable learning actually works.
The Developer Analogy
Think about how you learn best as a developer.
Have you ever tried to learn a new framework by reading the docs from page one to page done? How’d that go? You probably retained about 15% and forgot the rest by the time you needed it.
Now think about a time you learned a framework because you needed it for a project you cared about. You had a problem, the framework solved it, and you learned exactly what you needed as you went. You probably retained way more, and the learning was faster and more enjoyable.
That’s interest-led learning. It’s how adults learn best, and it’s how kids learn best. The only difference is that adults can sometimes force themselves to grind through boring material. Kids 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 approach:
1. Identify the current obsession. What does your kid talk about nonstop? What would they choose to do all day? That’s your vehicle.
2. Map concepts to the interest. Take the computational thinking concepts you want to introduce (sequencing, patterns, conditionals, decomposition, debugging) and brainstorm how they connect to the obsession. I promise they do.
3. Let the kid drive. Don’t say “let’s learn about patterns using trucks.” Say “hey, I noticed the garbage truck always goes to the same houses. Does it go in the same order? Why?” Let the concept emerge from the conversation.
4. Build something. This is where it gets really powerful. “Want to make a garbage truck game?” takes the interest and adds creation. Now your kid isn’t just learning concepts — they’re applying 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 to add a dinosaur that rides on top, go with it. The tangent is just another interest expressing itself. The concepts still apply.
The Hard Part
I’ll be honest: interest-led is harder in some ways for the parent than curriculum-led. A curriculum tells you what to do each day. Interest-led requires you to improvise, to find the computational thinking in whatever your kid is currently obsessed with, to think on your feet.
But it’s also more fun. Because you’re responding to a real kid with real enthusiasm, not marching through someone else’s lesson plan. And the results speak for themselves: deeper engagement, better retention, and a kid who associates learning with their favorite things instead of with obligation.
And if the only thing they retain from your lessons is a love of learning, that’s more than enough.