If you're 12 and want to build things

Most of what gets written about kids and coding is written to the parents. This one is to you. If a grown-up is reading it to you out loud, that's fine, but the sentences are pointed at you, not them. The reason is simple: you're the one who has to do it. They can drive you to a class. They can't build the thing.

So, you're twelve, give or take, and you want to build things. Here is what I'd tell you if you sat down next to me at the workbench.

Don't start with "pick a language"

Every list on the internet will tell you to pick a programming language first. Python or JavaScript, usually. Big debate.

Skip it. The language is the smallest decision you'll make. Languages are mostly the same shape — variables, loops, functions, ways to talk to other things. Learn one well and the next one takes a week. Pick whichever one is in front of you. JavaScript runs in your browser. Python is what most people end up writing eventually. Pick one, move on.

What matters more is the shape of how the internet works. Three things, in order:

1. Request and response. Your browser asks for a thing. A server gives back the thing. That's almost everything. Every website, every app, every AI tool — that shape underneath. Learn what a URL really is. What a server is. What JSON looks like when it shows up.
2. Data has a shape. Information lives in lists and tables and trees. Before you write any code, you sketch the data on a napkin. If you can draw it, you can build it. In any language.
3. Functions take stuff and give stuff back. That's the unit. Everything else is arrangements of those.

Understand those three and you're ahead of most college freshmen taking their first CS class. That's not a compliment — it's a statement about how the field is currently taught.

Build one real thing

Don't take a hundred tutorials. Tutorials are watching someone else go to the gym.

Pick one thing you actually want to exist. Not a calculator. Not a to-do list. A thing you want. Examples that have actually shipped from kids your age:

• A card game your sister will play
• A study tool that quizzes you on the stuff you keep getting wrong
• A bot that recommends what book to read next
• A page that tracks every dog you see in the neighborhood
• An AI Pokédex that identifies the bug you found in the yard
• A trivia game about your favorite show, for your group chat

The rule is: somebody, somewhere — a sibling, a friend, your grandma — ends up using the thing. Not a screenshot. Not a demo. Use.

That one constraint changes everything. It changes what you build, how you finish it, what you cut. You will learn more from one thing somebody uses than from ten things that sit in a folder.

You will use AI. That's the point.

You're going to use AI to build. That's fine. A twelve-year-old in 2026 can do things a college kid couldn't do five years ago, because the AI does the part that used to take the most time.

The rule that matters, the only one:

Don't ship code you can't read.

If the AI hands you something and you don't understand it, you don't get to put your name on it yet. Slow down. Ask the AI to explain it. Ask a person. Run it. Break it on purpose to see what happens. Then put your name on it.

This is the line between a kid who uses AI and a kid who builds with it. One of those depreciates the second the next model ships. The other one keeps working forever.

The order

If I were starting today, knowing what I know:

1. Learn what HTML, CSS, and JavaScript actually do. A weekend. Maybe two.
2. Build a one-page website that does one thing you find useful. Ship it to a URL.
3. Learn what an API is. Wire your page to a real one. (Weather. Pokémon. Something fun.)
4. Add an AI call. Use it for the part you couldn't have done alone.
5. Give the URL to a person who is not a parent. Watch them use it.
6. Fix the three things that broke when they used it.
7. Do it again with a bigger idea.

Steps 1 through 4 are about eight months at an hour a couple times a week. Steps 5 through 7 are the rest of your life.

You don't need permission. You don't need a curriculum. You don't need a certificate. You need an idea, a browser, and the patience to be bad at it for a month.

The door isn't locked. Start.