You have built games, a website, micro:bit programs, and even trained an AI model. Today you pick one thing you already care about (another subject, a hobby, a local issue) and build something small that connects coding to it.
By the end you will have a short working build that shows data, interactivity, or a short coded performance, and you will show classmates one thing it does and why it matters to you.
Keep this tight. Name the goal in one breath: a small cross-curricular build using tools they already know, finished with a quick show-and-tell. Do not spend time recapping every tool from the strand; they will choose as they go.
If anyone freezes on the blank page, point them at the four starter ideas on the next step rather than inventing a fifth.
Rules
- Connect coding to another subject or something you care about.
- Show data (a reading, a score, a count, a chart), interactivity (buttons, sensors, input that changes what happens), or a short coded performance (a tune, a drawing the pen makes).
- One feature only. Keep it small enough to finish today.
Four starter ideas if you want a launch pad:
- micro:bit environment station (needs kit): read light or temperature and show it, useful for science or geography fieldwork. Minimum version: show one light reading on the LED matrix.
- Scratch make-a-song (quick start): use notes or loops that match a music or Irish-language rhyme you know. Minimum version: one short four-note hook.
- Scratch pen art (quick start): draw a pattern or crest linked to art, maths shapes, or a club badge. Minimum version: one shape or crest outline drawn by the pen.
- Body-controlled game (needs webcam or model): use a pose or image model so movement steers something, good for PE or accessibility ideas. Minimum version: one pose moves a sprite left or right.
You may also invent your own idea with the same tools. One clear feature beats five half-built ones.
Done looks like: a short working build you can demo in under a minute, plus one sentence on how it connects to something outside coding.
Frame choice quickly, then get them building. Circulate and help undecided students pick one starter within two minutes.
Before you start the build timer, give a 30-second prompt: Pick starter 1 to 4 now or write your one-line idea. Decide before we start the timer.
Constraints that help
- One feature only. If they want a second, park it as "next time".
- They must already know the tool. No new platforms today.
- Pairs are fine if devices or micro:bits are short; each person still needs a clear role.
Starter setup costs: Starters 2 and 3 are quick starts on Scratch. Starters 1 and 4 need kit or webcam. Circulate first to anyone on 1 or 4 for a two-minute setup check. Starter 4 only if they reuse a model from the AI lessons or can train in under five minutes. Otherwise steer them to starters 1 to 3.
Default if still choosing after minute two of build: micro:bit one light reading on the LED matrix, or Scratch pen crest outline.
Recovery: if a saved earlier project is missing and they hoped to extend it, start a fresh mini-build from one of the four ideas instead of hunting files.
Watch for over-scoping (full weather apps, multi-level games). Pull them back to one sensor reading, one chorus loop, or one steering control.
Build your small project now.
- Write one line at the top of a comment, note, or page title: what it connects to (for example "science: classroom light levels" or "music: a four-note hook").
- Build the core feature first until it runs: a reading on screen, a sound that runs, a drawing that appears, or an input that changes something.
- By halfway, your core feature must run once. If not, cut scope to the starter's smallest version.
- Add only what the demo needs. Test after every small change.
- When it works, save your project so you can open it again later.
When something breaks: say what went wrong, check the last block you added, try one fix, undo if it still fails.
Leave a few minutes at the end of this step so you are ready to demo one thing it does.
This is the bulk of the lesson. Stay off the board unless a whole-class snag appears. Circulate with three prompts: What subject or interest is this for? What is the one feature you will demo? Does it run right now?
Enforce the one-feature rule in the first two minutes of build. Anyone still choosing after minute two gets the default: micro:bit one light reading, or Scratch pen crest.
At about +13 minutes, call a mid-build checkpoint aloud: core feature must run once now; if not, cut to the starter's minimum version.
When students test, use a quick predict beat before they run: What do you expect to see or hear when this runs? Then they run and compare. Keep it to one sentence; do not stop the room for a full PRIMM cycle.
Look-fors
- A clear non-coding link, not just "a game I like".
- Data, interactivity, or a short coded performance actually visible in the demo.
- Students testing as they go rather than building blind for twenty minutes.
Differentiation: stuck students pick starter idea 1 or 2 and ship a tiny working version. Strong finishers polish the connection (a label, a second reading, a short on-screen instruction) rather than starting a new project.
Remind the class five minutes before the end of this step to save and prepare their one-minute demo line.
Show your build in a short round.
- In a small group, each person gets about one minute.
- Demo one thing the build does (run it, do not only describe it).
- Say in one sentence how it connects to another subject or something you care about.
- Listeners name one strength only, then swap to the next person.
If your build is not fully finished, demo the part that works and say what you would add next.
Run tight groups of three or four so everyone speaks. Keep a visible timer if groups drift. The rule is one strength only: no long critique rounds.
If a build fails live, treat it calmly: the student still states the intended link and what the working part did in testing. That still meets the show-and-tell goal.
Collect nothing written. The point is spoken connection plus a live demo.
Pull together what the builds had in common. The strongest ones were small, ran for real, and had a clear link outside coding: a subject, a hobby, a local need.
That is the same move you will use later when you choose a bigger project: start from something that matters, then pick the coding tools that serve it.
Take two or three volunteer links only (for example science data, music, PE movement). Name the pattern: coding is the tool, the interest is the reason. Do not reopen full demos.
Unlock the full learning experience
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.
This lesson is copyright of Coding Ireland 2017 - 2025. Unauthorised use, copying or distribution is not allowed.