Hi, BotExplainer Read the postPost

Under the hood

Ages 10–16About 3 min9 scenes

Bots are programs that talk back.

What a bot actually is: under the hood, not the marketing. Strip the branding off, and a bot is one of the oldest ideas in computing.

Not magic. Not necessarily AI. A loop with ears. Press Next to start (arrow keys work too).

One word, too many things

The word bot is doing too much work.

A kid says she wants to build a bot. She might mean any of these. Which ones are programs that talk back?

Program vs. bot

A program runs once and stops. A bot runs until you tell it to stop.

Program
print("Hello")add(2, 2)print("Done")

Output

Bot
while running: message = wait_for_message() reply = decide(message) send(reply)

Not started.

Messages answered: 0

Same language. Different shape. The bot is built around waiting and responding.

The shape shows up everywhere

The surface changes. The skeleton does not.

The skeleton
Wait for
Decidedecide()
Respond with

↺ repeat

Kids who learn to see the skeleton (input, decide, output, repeat) can build any of these without treating them as separate subjects called “web dev” and “robotics” and “AI.” They are all programs that talk back.

The decide step

Waiting is boring. Sending is boring. Decide is where it gets interesting.

Talk to it

Kids need both pictures. The chatbot is a bot. The if-statement doorbell script is also a bot. Some use rules. Some use models. All of them talk back.

For parents and teachers: why both pictures matter

Confusing the two leads to either mysticism (“AI is sentient”) or dismissal (“bots are just fancy search”). Neither is true. Bots are programs. The skeleton is still wait → decide → respond; with a model, the decide step just got very large and very fuzzy.

Bots need a place to live

A bot needs a host: somewhere to sit while it waits.

A program that runs once can live on your laptop, finish, and close the tab. A bot is a long-running process, and long-running processes need a home.

Where does the waiting happen?

Listening

For parents and teachers: the week the bot needs to stay awake

Kids get stuck not because the bot logic is hard, but because nobody told them the bot is a long-running process. Where your app lives is not a chapter for “later.” It is the chapter for the week the bot needs to stay awake.

Bots are interfaces

Channel first. Logic second.

A Discord bot
is an interface to your code, reachable through chat.
A chatbot
is an interface to a model, reachable through language.
A robot
is an interface to motors and sensors, reachable through the physical world.

Ask: who is talking to it, and what should they be able to make happen?

Match each request to the bot it needs.

The responsibilities that come with ears

A bot that listens collects things. The builder is responsible for them.

A bot that runs forever and breaks annoys everyone who was counting on it. A bot that listens collects messages, voice, images, locations.

Design a quiz bot for your Discord server. Answer four questions before it goes live.

For parents and teachers: ethics as a design constraint

We teach this the same way we teach responsible AI: not as a lecture at the end, but as a design constraint at the beginning. The ethics are not separate from the engineering. They are part of the decide step.

How to build your first one

Pick the smallest bot that has a real user. Write the loop on paper.

Your first bot

Five steps

Under 13? Many chat apps require users to be 13 or older. Build it with a parent or teacher.

Then, when the loop is muscle memory, swap a rule for a model. The bot gets smarter. The skeleton does not change.

Build one. Make it talk back. Then make it worth listening to

Read the full post on Hi, Bot Where your app lives How we think about safety