Should my teen learn to code or build with AI? A teacher's answer

This question usually comes up right after a parent has watched an AI tool build a working app in a few minutes. "Is there any point in my teen learning to code anymore? Or should they just learn to build with AI?"

It's a fair question, and I hear it often. I teach teenagers live online and build with AI tools most weeks, so I've thought about it from both sides. My answer is both, in a particular order. Start with something your teen wants to make, let AI do most of the work at first, and then, week by week, look inside what it built and learn how it works.

Below is my reasoning, and what that looks like in practice.

Why parents are asking now

A few years ago the path was obvious. A curious teen learned a language like Python, worked through exercises, and maybe built a small game after a few months.

Now you can describe what you want in plain English, and an AI agent writes the code, sets up the project and puts it online. I build with Replit Agent, and the first time you watch it work, it changes what you think "learning to code" means.

So it's reasonable to ask. A year of syntax exercises is hard to justify next to a tool that produces something similar in an afternoon.

But "the tool can write the code" and "my teen can build something that works for other people, and fix it when it breaks" are very different things. That difference is what I want teens to learn.

What I mean by building with AI

When I say building with AI, I mean a loop like this:

• Pick a problem that someone you know has.
• Describe a small first version clearly enough for an AI tool to build it.
• Test it, find what's broken, and either explain the problem back to the tool or fix it yourself.
• Put it in front of a user, listen, and improve it.

Every step is a skill. Describing exactly what you want is hard. Testing properly is hard. Listening to someone tell you your app is confusing is very hard, especially at fifteen.

These skills are useful in almost any job, whether or not your teen ever writes code for a living.

What coding still teaches

Learning some code is still worth it, even when AI writes most of it, because of the way of thinking it trains.

When students learn the basics, they learn to break a big problem into small steps. They learn that computers do exactly what you typed, whatever you meant. They learn to read an error message without panicking, and to trace a problem back to where it started.

That last one matters most. AI tools make mistakes, sometimes very confidently. A teen who knows a bit about code can look at what the AI made and say, "That's wrong, the data isn't being saved." A teen who doesn't will keep typing "fix it" and hoping it works.

Where teens get stuck with AI alone

When teens build with AI and nothing else, the same problems tend to show up.

They can't tell when something's wrong. The app looks finished, so they assume it works. They get stuck in loops, asking the tool to fix the same bug over and over while the project gets messier each time. And they can't explain their own work, which becomes a problem as soon as a teacher, a user or an interviewer asks, "How does this part work?"

The tool itself is fine for teens to use. What makes their projects fragile is having no understanding of what it has built.

Where teens get stuck with syntax alone

The other path has its own problem, and it's just as common.

A teen starts a coding course, learns loops and variables, and loses interest before building anything they care about. The exercises feel random. They know what a for loop is, but they've never made something another person used.

For most teenagers, motivation comes from making something, showing it to people, and hearing someone say, "Wait, you made that?"

Build first, learn the code along the way

This is how I'd approach it with teens aged 13 to 18.

Start with a project. The teen picks a problem they care about, like a study planner, a booking page for a family business or a website for their club. The project gives every lesson a reason to exist.

Let AI do the first draft. With an AI building tool, they get a working first version fast. That early success keeps them going through the harder weeks.

Look inside, one piece at a time. Each week, look at one part of what the AI built. What is this file doing? Where is the data stored? What happens if I change this line? They pick up variables, functions, databases and how the web works because their own project needs them.

Make them explain it. At the end they present what they built and how it works. If they can explain it to a group, they understand it.

That's how I approach it in my own tutoring, one-to-one and in small groups on Zoom.

What this looks like at different ages

This is a rough guide, and every teen is different.

Ages 13 to 14. Focus on building, curiosity and explaining things clearly. Keep projects small and personal. Introduce code by reading and tweaking it before writing any from scratch.

Ages 15 to 16. Add structure. Plan before building, test with users, and learn a few core programming ideas properly.

Ages 17 to 18. Go deeper. Write some code by hand, understand how the parts of an app connect, and think about privacy in what they build.

If your teen wants to study computer science later

If your teen has their eye on computer science at university, I'd still push for proper study of the fundamentals through their school courses. Building with AI doesn't replace that.

What it adds is proof that they can make things. A teen who has built and launched a product, and can explain their choices, has something concrete to talk about. I can't promise that leads to a particular admission or job, and nobody can. But it gives them far more to talk about than a list of finished tutorials.

Questions to ask before you pick a course

Whatever you choose, these questions help separate the good options from the flashy ones:

• Will my teen build something for an actual user, or just follow along?
• Is there a live teacher who can see where my teen is stuck?
• Will they learn why the code works, or only how to prompt?
• How does the course handle privacy, age rules and honest use of AI?
• Do they have to present or explain their work at the end?

A course with good answers to these will usually teach your teen both.

If you'd like your teen to learn this way, here's how my tutoring works.