Computers in Everyday Life
Identifying computers in everyday life — not just laptops but phones, tablets, smart speakers, traffic lights, washing machines; what makes something a computer
Lesson: Computers in Everyday Life
Subject: Computing · Domain: Artificial Intelligence · Age band: 5–7 · Type: Conceptual
Centrality: 0.029 (foundational awareness — unlocks several branches)
Taxonomy ID: mt_XbGfVhfiUz
Standards: (none pinned to this topic in dataset)
Tailored for: Gifted 5y9m child, IQ 125–130+, asynchronous — math 2–3 grade, reading 98th percentile, developmentally 5
Why this matters
Your son lives in a world saturated with computers, but most five-year-olds (even very bright ones) have a narrow mental category for "computer" — it looks like a laptop or maybe a tablet. This lesson widens that category dramatically. Once he sees that the microwave, the traffic light, the washing machine, and the smart speaker all share something essential, he has the conceptual foundation for every downstream topic: algorithms, programming, AI, robotics.
The deeper gift here is the thinking habit — looking at an everyday object and asking, "Is there something inside following instructions?" That question is the spine of all computer science. You're not teaching vocabulary. You're teaching a lens.
Your son may already casually know that "phones have computers in them." That's surface-level. The goal is the generalization — what do ALL computer-containing things have in common, and how would we decide about something we've never seen before?
Learning objective
Your son will identify computers in everyday objects (including non-obvious ones) and explain what all computers have in common — they follow instructions and process information.
Sentence you want him to be able to say: "A computer is something that follows instructions to work with information — that's why a washing machine is a computer but a toaster mostly isn't."
Before you sit down together
Materials
- A basket of household objects or pictures of them — mix of computer-containing and non-computer-containing. Aim for variety: a phone, a book, a mechanical egg timer, a digital clock, a toy with buttons, a smart speaker, a wooden spoon, a remote control, a hair dryer, a bicycle. The contrast is what teaches — not the examples alone.
- Two sheets of paper — label one "Has a computer inside" and the other "No computer inside." Large, clear. He'll sort objects onto these.
- A marker — for him to draw or write, not you.
- Optional: a screwdriver you don't mind not using — if he asks "what's inside?" you can say we could look, but we don't need to open things to reason about them. That's a powerful idea on its own.
Rationale: physical sorting builds stronger mental categories than talking alone. Bright kids often skip the concrete phase and then have fragile concepts. Let him handle objects.
Best time of day for this lesson
Mid-morning, after a snack and some physical movement, tends to work well for conceptual lessons — his brain is fed, his body has moved, and he's not yet in the post-lunch dip.
Avoid: right before a screen he's anticipating (he'll rush), or when he's tired (conceptual generalization is the first thing to go).
Activity: "What's Hiding Inside?"
A 15–20 minute sorting and reasoning game. Structure follows Introduce → Explore → Apply → Wrap-up.
Phase 1: Introduce (3–4 minutes)
Sit on the floor or at a table. Put the basket between you. Don't announce "we're learning about computers" — that flattens curiosity.
Sample dialogue:
"I've got a basket of stuff here. Some of these things have a computer hiding inside them — secretly! — and some don't. I want to know if you can figure out which is which. But first — what do you think a computer even IS? Like, if something has a computer inside, what does that mean?"
Listen carefully to his answer. This is your diagnostic. If he says "it has a screen" or "it's electronic," you've found the gap to work with. If he says "it follows instructions" — skip ahead, he's further along.
Phase 2: Explore (6–8 minutes)
Pull objects out one at a time. For each, ask: "Does this have a computer inside? How do you know?"
Don't correct immediately. Let him reason, even if he's wrong. If he says the egg timer has a computer because it "counts," you might say:
"Interesting — it does count down. Hmm. But does it FOLLOW INSTRUCTIONS that someone gave it? Or does it just... do the same thing every time because of how it's built? What do you think?"
This is the conceptual meat. The distinction between mechanical behavior (gears doing one thing) and computational behavior (following changeable instructions) is the whole lesson.
Key objects to spend time on: - The washing machine or microwave — these follow programs. Different cycles, different times. That's a giveaway. - The mechanical egg timer — it "knows" time, but it can't be told to do something different. It's not a computer. - The remote or smart speaker — these send instructions or respond to them.
Phase 3: Apply (4–5 minutes)
Spread the two labeled papers out. Ask him to sort the whole basket.
Then ask the synthesizing question:
"Look at your 'has a computer' pile. What do ALL of them have in common? Not just screens, because the washing machine doesn't have a screen. Not just buttons, because the remote has buttons but so does a mechanical toy. What's the REAL thing they share?"
Guide toward: they follow instructions and process information. If he gets close in his own words, celebrate that — his phrasing doesn't need to be perfect.
Phase 4: Wrap-up (2–3 minutes)
Sample dialogue:
"So here's the big idea — a computer is something that follows instructions to work with information. That's why your tablet is a computer, and the traffic light on the corner is a computer, and even the cash register at the store has a computer inside. They're everywhere once you start looking. Can you think of one more thing in this room that might have a computer hiding inside?"
End on that curiosity question. Don't test. Don't quiz. Leave him wondering.
Kid-response scripts
| He says... | What's happening | You might try... |
|---|---|---|
| "Everything electronic has a computer!" | He's using "needs electricity" as proxy. Common overgeneralization. | "Hmm — is a light bulb a computer? It uses electricity. Does it follow instructions? Can you tell it to do something different?" |
| "The toaster has a computer because it's smart." | "Smart" is vague; he may not know what he means by it. | "What does the toaster actually DO? Does it follow different instructions, or does it just... get hot for a while?" |
| "A remote control isn't a computer, it's just buttons." | He's using appearance (no screen) instead of function. | "You're right it's not a FULL computer. But it has a tiny computer inside that SENDS instructions to the TV. Want to think about what 'sending instructions' means?" |
| "I already KNOW this, this is easy." | He likely knows the surface — devices have chips. He may not know the generalization. | "Okay — quick one. What's the ONE thing all computers have in common? Not screens, not buttons — the real thing." If he nails it, jump to Stretch. |
| "A car is a computer." | Interesting! He may be right or overgeneralizing. | "Parts of a car have computers inside. Which parts do you think? What would those computers be telling the car to do?" |
| "A book isn't a computer but it has information." | Sharp observation — he's testing the boundary between information storage and processing. | "Ooh, good one. A book HOLDS information, but can it FOLLOW INSTRUCTIONS or make decisions? What's the difference?" |
| (Silence, staring at the pile) | He's processing. Gifted kids sometimes go quiet when generalizing. | Wait. Count to ten slowly in your head. If still stuck: "Want a hint? Think about what YOU do when you follow a recipe..." |
Common misconceptions to watch for
| What you see | What's actually going on | How to gently address |
|---|---|---|
| He says "it has a screen, so it's a computer" | Using visible feature (screen) instead of underlying function (follows instructions) | Present counterexamples: washing machine (computer, no screen), old TV (screen, arguably not a computer in the processing sense) |
| He says "everything that plugs in is a computer" | Conflating electricity with computation | Lamp, fan, heater — all plug in, none compute. The question isn't power, it's instructions + information |
| He insists a mechanical toy "has a computer" because it moves | Blurring mechanical and computational — they both "do something" | "It does move! But can you give it NEW instructions? Or does it always do the exact same thing?" — this is the key test |
| He calls everything "smart" without defining it | "Smart" has become a contentless label | "What does 'smart' actually mean? Can you say it without using the word smart?" |
| He's bored and sorting without thinking | Surface task is too easy; the generalization hasn't been demanded yet | Jump to Stretch immediately. The sorting isn't the lesson — the why is. |
Stretch (where the real lesson lives for your son)
Your son may sort the basket in two minutes flat and say "done." That's not the lesson — that's the warm-up. The lesson is the transfer and the edge cases. Try any of these:
1. The "What Would It Need?" Game (5 min)
Pick a non-computer object — a toothbrush, a shoe, a jacket. Ask:
"If we wanted to make this into something WITH a computer inside, what would the computer DO? What instructions would it follow?"
This is toy-level product design and it's where computational thinking starts. A "smart toothbrush" might count brush time. A "smart jacket" might check temperature and warm itself. He's now reasoning about what computers are for, not just where they hide.
2. The Spectrum Sort (5 min)
Instead of two piles, make a line: "Definitely a computer" → "Maybe" → "Definitely not."
Where does a digital watch go? A smart watch? A mechanical watch? A microwave with one button? A microwave with twelve programs?
The "maybe" pile is the richest. Ambiguity is where understanding lives.
3. The "Is a Human a Computer?" Question (5 min)
"A computer follows instructions and processes information. You follow instructions and process information. Are YOU a computer?"
This is a genuine philosophical question in computer science (Turing, von Neumann, modern cognitive science). Let him wrestle. There's no rush to a "right" answer. The wrestling is the point.
Some kids say "no, because I have feelings." Others say "yes, because my brain is like a computer." Both are interesting. Follow up: "What's the difference between a brain and a laptop?"
4. Invisible Computers Hunt (5 min)
"Computers are hiding in places you can't see. Let's walk around and each find three things that have computers inside that you CAN'T tell just by looking."
Traffic lights (the controller), the thermostat, the refrigerator, the car, the elevator. This builds the sense that computation is infrastructure — it's everywhere, quietly running the world.
5. The "What Instructions?" Game (5 min)
For each computer-containing object he found, ask:
"What INSTRUCTIONS is that computer following? If you could read its mind, what would it be saying to itself?"
The washing machine: "Fill to this level. Heat to this temperature. Spin for 18 minutes. Drain. Spin again." The traffic light: "Green for 30 seconds. Yellow for 5. Red for 30. Repeat."
This is his first encounter with programs as instructions computers follow — and it's the direct bridge to the next topic (Step-by-Step Instructions).
Quick mastery check (60 seconds)
- [ ] Can he name at least five everyday objects that contain computers, including at least two that don't look like traditional computers (no screen/keyboard)?
- [ ] Can he explain in his own words what all computers have in common — using the ideas of "instructions" and "information"?
- [ ] Can he correctly sort a novel object he hasn't seen before into "has computer" or "no computer" and justify his choice by function, not appearance?
Formal mastery check
From the topic's evidence field:
- Point out at least five everyday objects that contain computers — including non-obvious examples (washing machine, traffic light, thermostat, etc.)
- Explain what all computers have in common — they follow instructions and process information
- Sort a set of objects into "contains computer" and "does not contain computer" — with reasoning, not guessing
If all three are solid, move on. If one is shaky, spend time on that specific strand before advancing.
Vocabulary to use naturally
- Computer — something that follows instructions to process information
- Instructions — the steps a computer follows (also called a program)
- Information — the stuff a computer works with (numbers, words, signals)
- Process — to take information in, do something with it, and produce output
- Program — a set of instructions, like a recipe for a computer
- Sensor — how some computers "know" about the world (temperature, light, touch)
Drop these in naturally. Don't pre-teach them as a list — use them in context and he'll absorb them.
What comes next
This topic is a hard prerequisite for three downstream topics:
- Step-by-Step Instructions — now that he knows computers exist everywhere, the next question is: what exactly are the instructions they follow? This leads directly into algorithms and sequencing.
- Smart Versus Not-Smart Devices — he can now reason about what makes a device "smart" (it has a computer that follows instructions) versus a regular device.
- Real-World Robots — robots are computers that also move and sense. Understanding computers comes first.
The natural next lesson is Step-by-Step Instructions — because it answers the question this lesson raises: "What are the instructions computers follow?"
If this lesson didn't land
-
Try a different setting — some kids engage better walking through the house touching real objects rather than sorting from a basket. Make it a treasure hunt.
-
Shorten and narrow — if he's overwhelmed by the generalizing question, drop it for now. Just do the sorting. Come back to "what do they have in common?" another day. Conceptual understanding often consolidates after the experience, not during.
-
Check the prerequisite — there are no hard prerequisites for this topic, but if he's not engaging, he may need more exposure to the idea that machines can follow instructions. Try having him "be a robot" while you give him instructions to walk to the kitchen. That's the embodied version of this concept.
-
Flip the order — if the sorting feels flat, start with the Stretch activity "What Would It Need?" (designing a smart toothbrush). Sometimes creating computer-containing objects builds the concept faster than identifying them.
-
Wait a week and try again — he's five. Some concepts just need a little more life experience to hook onto. The world will give him examples every day. Point out one or two casually this week ("that traffic light has a computer inside, telling it when to change") and try the lesson again later.
Source
Taxonomy ID: mt_XbGfVhfiUz
Dataset: Computing / Artificial Intelligence domain
Standards: (none specified for this topic)
Generated for: Gifted 5y9m, IQ 125–130+, asynchronous development