How is this different from a coding camp?

What coding camps do well.

Before the comparison, the credit. A good coding camp is a real thing, and the kids who come out of one have skills that don’t appear from nowhere else. Three of those skills are durable.

The first is syntax fluency. A week or two with Python or JavaScript builds a working vocabulary: variables, loops, conditionals, functions. Resnick’s group at the MIT Media Lab calls this the “floor” of a creative computing environment, and a camp’s explicit job is to raise the kid up off that floor so they can read code without flinching.¹ Reading code is the prerequisite for everything else, and camps are good at it.

The second is debugging muscle. A kid spends two hours trying to make a sprite move and the answer turns out to be one missing semicolon. That experience, repeated, builds a kind of patience that’s hard to teach any other way. Papert wrote about this in 1980: the kid who has fought a computer over a semicolon has learned something about precision that the kid who only ever drew in crayon has not yet learned.²

The third is group dynamics. Coding camps put a roomful of kids next to each other, and the social texture of that room does a lot of pedagogical work. Kids see each other’s screens. They borrow ideas. They get unstuck by leaning over to a neighbor. Yasmin Kafai and Quinn Burke documented this peer dynamic at length in Connected Code, arguing that the social context of making is half the learning.³ Camps deliver this almost as a side effect.

If your kid is the kind who already wants to write code, and you can find a camp run by people who actually like teaching kids, sign them up. None of what comes next is an argument against that.

What coding camps tend to skip.

The thing camps are not shaped to deliver, because the format doesn’t leave room for it, is the part that happens before a kid wants to write code.

A camp’s curriculum has to assume the kid is motivated. The week is short. There are exercises to get through. The path is “teach the concept, do the exercise, build the canned project at the end.” This is fine when the kid arrives already wanting to build something. It’s less fine when the kid hasn’t yet discovered what they want to make. The motivation has to be supplied externally: by a parent who enrolled them, by a teacher who’s nice, by the social pressure of the room. Once the camp ends, the motivation tends to end with it.

The second thing camps don’t cover, because it’s newer than most curricula, is AI literacy. A kid who learns to write a for-loop in 2026 is also, whether the camp acknowledges it or not, learning to write that for-loop next to an AI assistant that can write it faster. The question of when to ask the model, when to write it yourself, and when to doubt the model’s answer is the actual modern coding skill. Duri Long and Brian Magerko mapped out five competencies that this skill decomposes into, and most camps don’t teach any of them.⁴

The third thing camps skip, because it’s harder to put on a syllabus, is taste under constraint. Bret Victor argued in his 2012 essay on learnable systems that what programmers are really doing is building intuition through immediate feedback: try a thing, see what it does, adjust.⁵ That intuition takes hundreds of small decisions on a project the kid cares about. A one-week camp doesn’t have time. The camp project is finished on Friday whether the kid loved it or not.

What Tell and Show is shaped for.

The studio is shaped around a different bet. Most 8–12-year-olds don’t walk in wanting to learn Python. They walk in wanting to make a game where a chicken fights a robot, or a story about their dog, or a website for their reading club. Syntax is an obstacle to that. The studio’s job is to keep the kid in the creative loop and let the AI partner handle the syntax until the kid wants to look at it.

The shape of the loop is artifact-first. The kid declares what they want. Inkie proposes a change to the project. A ChangeDisclosure card shows what’s about to be touched. The kid keeps, reviews, or undoes. Then they declare the next thing. It’s a tight loop and the kid is doing the choosing every time around.

Three differences from a camp follow from that loop. The studio is indefinite: a kid can stay for months, not a week, because the artifact keeps growing. The studio puts the kid in collaboration with AI instead of in adversarial debugging against a compiler. And the output is a real, shippable artifact: a hosted URL, a published film, a story other people can read. Camp projects end when the camp ends. Studio projects live somewhere.

None of that means the studio replaces a camp. It means the studio is doing a different job. The camp’s job is to teach the language of computers. The studio’s job is to teach the creative loop a kid uses an AI partner inside.

Side-by-side, honestly.

Five dimensions cover most of what parents want to compare. Here they are laid out, with the honest version of each side.

A camp’s curriculum has to assume the kid is motivated. The studio is shaped to produce that motivation, by handing the kid an artifact worth working on. On the order of operations

The table is honest. There are camps that do AI-aware curricula well, and there are studio sessions where a kid just messes around for an hour without shipping anything. The aggregate shape is what we’re comparing, not the best instance of one against the worst of the other.

Which one comes first?

The order question is the one parents actually want answered, so here’s the version we’d give a friend.

For most kids 8–12, the creative loop comes first. A kid who has shipped a game, a story, a site, or a film of their own has a reason to learn what a for-loop is. That reason carries them through the rough patches a camp puts in front of them. The camp lands. The syntax sticks. The kid is no longer the kid who showed up at camp because their parent signed them up; they’re the kid who showed up because they want to do a thing they already know how to imagine.

For a kid who has decided on their own that they want to write code, a camp is a great next move. Especially if it’s taught by people who like kids and who are honest that syntax fluency is one ingredient of many. Pair it with continued artifact work and the camp’s lessons get applied immediately.

For a kid who hasn’t yet caught the maker bug, a camp before the studio is more of a coin flip. Some of them come home in love with Python. Some of them come home glad it’s over and a little inoculated against the whole idea. The studio is the lower-risk first move because it doesn’t require the kid to fall in love with syntax to enjoy the loop.

Two real things, doing two real jobs. The honest answer is “both, in the right order, with the loop first.” If you can do exactly one this summer, do the one that keeps producing motivation after the week ends.