Coding for teens aged 13–15: code that sounds and glows

At thirteen, “exercise” tasks stop working — you need to make something you like. In the 13–15 lab, code drives music and light: a four-note melody lights up a garland by itself, and that’s only the start.

melody = ["C", "E", "G", "C"]
for note in melody:
    piano.play(note)
    garland.pulse(note)

What the teen does

Four notes in a list, a loop over the notes — and every note lights its own bulb. Then functions so as not to repeat code; their own melodies; light that reacts to rhythm; a night light that fades by morning. The projects already look real: with versions, with history, with something to show friends.

What they learn

Lists, loops, functions — as tools, not topics. To split an idea into parts and put it back together. To keep a project going longer than one session. To read someone else’s code — Hush sometimes brings a fragment and asks what it does. To check the assistant’s answer rather than take it on faith.

What a session looks like

This route is being prepared for 1 January 2027. The activities described here are a programme in development. We plan computer and tablet access, short tasks and saved progress for taking breaks.

What parents see

The future parent dashboard is planned to show projects and skills. It is not open yet. Standalone exercises on this site need no registration and offer a first look at our approach.

Frequently asked questions

Won’t a teenager get bored?

Boredom comes from box-ticking tasks. Here the task is to make a thing that sounds and glows, and show it.

Is this exam or competition prep?

No. It’s a workshop. Plenty will help at school too, but the goal is to make something of your own.

Can they start with no experience?

Yes. The first lab starts with four notes.

Opening on 1 January 2027. Routes for ages 7–9, 10–12 and 13–15 are in development. Try a first exercise without registering.