There’s no shortage of developmental milestone charts. Rolling over by four months. First words by twelve. Riding a bike by five. Pediatricians have these mapped down to the month.
Computational thinking, though – arguably the skill set that matters most in the 21st century – gets nothing but a vague nudge to “introduce coding” at some undefined later date, usually involving an eight-year-old, a $200 robot, and a lot of screen time.
When I went from engineering director to stay-at-home mom, it struck me that computational thinking isn’t some future course I’d need to remember to enroll my kid in. Toddlers do it every single day – when they play with blocks, pick out their clothes, or negotiate for “one more story.” So I wrote the guide to toddler CS milestones I went looking for and couldn’t find.
This isn’t armchair theory, though the research backs it up: Marina Umaschi Bers at Boston College has studied computational thinking in early childhood for over a decade, and Jeannette Wing’s foundational paper made the case that it’s a universal skill rather than a CS-major thing. Mostly, though, this is what I’ve watched happen with my own kid, lined up against what developmental science says to expect. If your child does some of these and not others, that’s normal. Kids aren’t firmware. They don’t all install features on the same schedule.
It is, however, useful to know what you’re looking at.
Age 1-2: The Hardware Installation
Think of this stretch as your child’s operating system booting up. They’re not “doing” computational thinking in any form you’d recognize yet. They’re laying down the prerequisite hardware: cause and effect, object permanence, basic categorization.
What you’ll see:
- Cause and effect loops. Drop the spoon, it falls. Drop it again, it falls again. Drop it thirty-seven more times, because clearly the experiment demands replication. This is your child discovering that actions have predictable, repeatable outcomes – bedrock for everything algorithmic that comes later.
- Basic sorting by a single attribute. All the red blocks in one spot. Every book pulled off the shelf (sorted by… reachability?). They can group by at least one feature: color, shape, size.
- Sequential imitation. Copying a two-step action: open the cabinet, pull out the pot. They can’t invent sequences yet, but they can copy short ones – the start of following instructions, which is the start of grasping what an instruction even is.
- Trial and error, no strategy. They’ll jam the square block at the round hole over and over, then succeed by accident with the right one. No hypothesis. Just brute force. (Though, in fairness, I’ve watched senior engineers debug exactly this way.)
What you won’t see (and that’s fine):
Planning. Abstraction. Multi-step reasoning. The prefrontal cortex is barely plugged in. Let it be.
What to do:
Narrate cause and effect: “You pushed the ball and it rolled!” Name categories out loud: “That’s a big one. That’s a small one.” Let them lose at the shape sorter – a little frustration is a fine motivator.
Age 2-3: First Programs
This is where it gets fun. Language explodes, and with language comes the power to describe a sequence instead of just imitating it. Your child starts writing their first programs without the faintest idea that’s what they’re doing.
What you’ll see:
- Verbal sequencing. “First shoes, then outside.” A two- or three-step plan, narrated before doing it. This is pseudocode – actual, literal pseudocode, just delivered by someone who pronounces “spaghetti” as “pasketti.”
- Multi-attribute sorting. “Big red cars here, small red cars there.” Two sorting criteria at once, which is a compound query: SELECT * FROM toys WHERE color = ‘red’ ORDER BY size.
- Basic if/then reasoning. “If it’s raining, we need boots.” They begin predicting outcomes from conditions. It isn’t reliable yet – they might also predict that putting boots on summons puddles – but the shape of conditional logic is there.
- Pattern completion. Red, blue, red, blue, red. They can extend a simple AB pattern, and some start inventing their own: “car, truck, car, truck.” This is the seed of algorithmic thinking – spotting a rule and applying it.
- Debugging with intention. The tower falls, and instead of a random retry they adjust: bigger block on the bottom this time. The hypothesis about why it fell might be wrong, but they’re forming one, and the method matters more than the accuracy.
What you won’t see:
Nested logic (“if it’s raining AND cold, boots AND a coat”). Abstraction past the concrete. Long multi-step plans. They’re still firmly tied to the physical and the present.
What to do:
Ask “what happens next?” constantly. Let them narrate routines, steps, recipes. Play pattern games with anything to hand – toys, food, sounds. When something breaks, say “why did that happen? Let’s look!” before you swoop in to fix it.
Building with AI at 2-3
My son and I built his first browser games with Claude right around here. He described what he wanted, I turned it into a prompt, and he played – and learned that his ideas can become things. His first one (“Make a red car game! Make it jump!”) quietly changed his whole relationship with a screen, from something he watched into something he made.
Age 3-4: The Abstraction Leap
Something shifts around three. I watched it happen in real time. Your child starts operating on representations of things rather than the things themselves. They can think about thinking – not philosophically, they’re three, but functionally.
What you’ll see:
- Representation and symbols. A stick becomes a sword. A box becomes a car. A line of couch cushions becomes a train. They’re using physical objects as variables – stand-ins for something else entirely. This is abstraction in the strict computer-science sense: stripping away the details that don’t matter so you can work with a simpler model.
- Algorithm narration. Not just “first this, then that” – they start dictating whole procedures. My son will explain how to make his favorite snack in six ordered steps and get genuinely annoyed if I deviate from the protocol. He’s writing a spec. He’s defining an API. He is, I’ll remind you, three.
- Conditional branching. “If you sit nicely at the restaurant, we’ll get dessert. If you’re disruptive, we leave.” Different inputs, different outputs – and they’ll start manipulating the conditions (“But I wasn’t THAT loud!”), which is really just penetration testing the parental permission system.
- Decomposition. “I want to build a BIG house.” Okay, what do we need? “A foundation. And walls. And a door. And a roof.” They can break a big goal into parts. Not always the right parts. But the instinct to decompose has arrived.
- ABC and ABB patterns. Beyond simple alternation now. Red, blue, green, red, blue, green. Or red, red, blue, red, red, blue. The pattern engine is getting more capable.
What you won’t see:
Recursive thinking. True loop comprehension – they’ll do things repeatedly without conceptualizing “repeat until.” Error handling beyond one level (“but what if the BACKUP plan fails?”).
What to do:
Build things together. Anything. Block towers, art projects, simple games. Specifying what you want, breaking it into steps, and adjusting when it goes sideways is the computational thinking curriculum. Ask them to explain what they made. “How does it work?” might be the single most powerful question you can ask a three-year-old.
Building with AI at 3-4
This is the age my son started describing more elaborate games and watching them appear on screen. The computational thinking is all in the specification. Listen to this one: “I want a game where you drive a train through a maze with the arrow keys and it picks up fallen branches and brings them to the garbage dump.” That’s a feature spec, from a kid who still puts his shoes on the wrong feet about 40% of the time.
What’s Next
He’s three. The developmental research (Bers , Wing , Frontiers in Education ) puts loops, nested conditionals, and real systems thinking in the four-to-six range. That’s where kids start building rule systems, optimizing their own little algorithms, and carrying abstract ideas from one domain into another.
I’ll write about it when I see it. Subscribe and you’ll get the ages 4-6 edition the same week I live it.
The Point
None of this needs a screen, an app, a robot, or a subscription.
The whole curriculum is four things: narrate what’s happening, ask questions, let them fail, and build things together.
The milestones aren’t a checklist – your kid might be a pattern-recognition wizard who could not care less about sequencing, and that’s completely fine. The point was never to grade your child. It’s to learn to recognize computational thinking while it’s happening, so you lean into it instead of walking right past it.
It’s happening right now. In the blocks, in the spoon drops, in the twenty-minute negotiation over whether pants are strictly required today.
You just have to know what you’re looking at.
I wrote the book on this – literally. 12 Weeks of Tech Projects to Build With Your Kid is the hands-on curriculum that turns these milestones into weekly activities. 12 weeks of projects designed for ages 2-6. No coding required. No screen dependency. Just you and your kid, building things that teach them to think.