Ask the chef, or build the toaster? Two ways to use AI
Most people use AI as an answer box: ask, get an answer, ask again. AI can also build a small tool that does the job without AI. A guide for kids 8–16 and the grown-ups helping them, with ideas by age and the safety rules that go with it.
November 19, 2026 · Hi, Bot
Most people think of AI as an answer box. You ask, it answers. Next time you want the same thing, you ask again.
AI can do something else too. It can build a machine for you, and after that the machine does the job with no AI at all.
The chef and the toaster
Say you have a video and you only want the sound. You could ask an AI to pull the sound out every time you need it. That's like asking a chef to make your toast every morning.
Or you could ask the AI to build you a toaster.
Building takes a little while. After that, you push the lever and toast comes out the same way every time. The toaster doesn't need the chef.
A file converter is that kind of toaster. You tell the AI, "Build me a page where I drop in a video file and get just the sound out." It writes the instructions, which are called code. Then you test it. If it works, you have a real tool. It doesn't call the AI again when you use it, it doesn't cost AI money to run, and it does the same thing to the same file every time.
Why AI can build tools at all
Code is just writing. A computer program is words in a special language, and AI is good at writing, so it's often good at writing programs. Programs can convert files, run games, sort photos, and even build other programs.
The converter probably isn't magic under the hood, either. A tool like this usually wraps free, open-source software that people have been improving for years. The AI just put the pieces together. That's worth knowing, because the people who wrote those pieces deserve credit, and their licenses say how the code can be used.
How to choose
There are two ways to use AI:
- Ask it to do the thing. Good when you need fresh thinking each time, like "Is this poem sad or happy?" or "What's a good name for my robot?"
- Ask it to build the thing that does the thing. Good when you want the same result every time, like converting files, renaming photos, or checking a list.
A simple test: if the same input should always give the same output, build a tool. If every question needs new judgment, ask the AI.
Building costs effort once. Asking costs a little money and energy every single time. If you'll do a job a thousand times, a tool usually wins.
One catch: some tools call an AI for one step inside them. Those bring the every-time cost back. Know which kind you built.
Never trust a toaster you haven't tested
AI can build a toaster that burns everything. Before you trust a new tool, try it on:
- a normal file, the kind you'll use most,
- an empty or tiny file, to see if it breaks politely,
- a weird file, like a very long video, an odd format, or a file with a strange name.
If it fails any of those, tell the AI exactly what happened and ask it to fix that. Then test again.
"Works forever" is also a little too strong. File formats change, and computers update. A tool might need a fix next year. Someone still has to look after it.
The real skill is saying exactly what you want
A vague request gets the wrong tool. "Make a converter" could mean a hundred things. "A page where I drop one video file, and it gives me back an MP3 of the sound, without uploading the file anywhere" is a tool you can actually check.
You can practice this with no screen at all. One person writes exact steps for a small task, like making a sandwich or drawing a house. A partner follows them exactly as written, like a computer would. When a step is vague, it goes wrong, usually in a funny way. Fix the steps and try again. Our plain-paper game Robot Route works the same muscle: you program a maze one exact move at a time.
Where do your files go?
This is the privacy part. A tool that runs on your own computer never has to send your files anywhere. A random converter website might upload your video to someone else's computer, and you can't see what happens to it there.
So it's a good question to ask about any tool, built by you or not: where does my file go? If you're not sure, don't use it on anything private, like family videos or school work with your name on it.
Grown-ups: a few honest notes
Age rules come first. Most AI products require users to be 13 or older, or to use a parent's account. Check the rules of whatever tool you use, and for younger kids, do the AI part together.
Start with a job, not the idea. "Let's turn this video into just the sound" lands better than an explanation. Let your kid watch the AI build the tool, then run it on three files together. Seeing it happen beats any analogy, including ours.
Don't run code nobody understands on private files. AI-written code can be wrong, and it can be unsafe. Test on throwaway files first.
Keep them in charge of the tool. The risk of "just have AI build it" is skipping the basics. Pair every build with one question: can you explain what it does? If the answer is no, that's the next thing to learn.
Ideas by age
- Ages 8–10: Use the chef-or-toaster story, then sort a list of jobs into two piles: build a toaster or ask the chef. "Rename 200 photos" goes in one pile. "Write a birthday poem for Grandma" goes in the other.
- Ages 11–13: Build a small tool together with an AI (with a grown-up's account if needed), look at the code, and run it on the three test files above.
- Ages 14–16: Read the code line by line and explain why the same file always gives the same result. Then ask the AI to add one feature, and test again.
It doesn't have to be code
A tool is anything that keeps working after the AI is gone. AI can help you make a spreadsheet, a lookup table, a weekly schedule, a checklist, or a game board. Each one keeps working with no AI at all.
And here's the sequel, if you want to go further. A converter is a tool. A tool that can build converters for any pair of file types is a machine that makes machines, like a factory that makes cookie cutters. We wrote more about that idea in Build the machine that builds the machine.
The short version: you can ask AI for an answer, or you can ask it to build something that answers for you. The second way is slower to start, then fast and cheap every time after. Just test it first, and make sure you can explain what it does.
› Keep reading
Get the next dispatch.
Occasional, never spammy.