Why start this young
Most young people meet computers as finished products: an app opens, a game loads, a video plays. They rarely see what sits underneath, and they almost never learn that much of it is open, shared and theirs to explore. Between the ages of 11 and 14, curiosity is high and confidence is still forming. It is an ideal moment to show that technology can be understood, not only used.
Open computing is a natural fit. Linux and open-source software are free to install, honest about how they work, and used across the real world, from phones to the servers behind the websites children visit every day. Learning them teaches both a skill and an attitude: you are allowed to look inside.
A six-day shape
Our BRAVE course runs over six days, each building on the last. The progression moves from ideas to hands-on practice to independence:
- Day one: the world of open source, what it is, who makes it and why sharing matters.
- Day two: exploring open-source software, including an exercise comparing what familiar tools would cost against free alternatives.
- Day three: the Linux terminal, and what responsible use means when a computer does exactly what you tell it.
- Day four: essential commands such as sudo, apt, curl, less and grep, with some safe fun along the way.
- Day five: SSH and the firewall, connecting to another machine and deciding who may connect to yours.
- Day six: a guest day, learner presentations and a certificate.
The rhythm of a session
Each session lasts about ninety minutes, and the structure stays the same every day: a welcome, a short recap of last time, two or three topics each with an activity, a quiz, and a small home task. The predictability is deliberate. When learners know the shape of the session, their attention goes to the content rather than to wondering what comes next.
Ninety minutes is long enough to reach real hands-on work and short enough to hold attention, provided nobody listens for more than ten minutes without doing something. Activities break up explanation constantly: typing a command, predicting what it will do, checking whether they were right. The quiz is light and fast, used to show learners what they now know rather than to rank them.
The home task is small on purpose. A learner who finishes it feels capable; a learner overwhelmed by it learns to dread the next session. One command to try, one question to ask at home, or one open-source app to find and describe is enough.
Responsibility from the first command
Teaching the terminal to young people carries a duty. The same commands that install software can remove it, and the same tools that connect to a server can be misused. We introduce responsibility alongside power, not afterwards. Before learners use sudo, they discuss why it asks for a password. Before they use SSH, they talk about permission and why you only connect to machines you are allowed to use.
Practically, learners work in their own safe environments, such as a dedicated Linux machine or virtual machine, where mistakes cost nothing. That freedom to break things matters: a learner who has deleted a test folder by accident, and recovered, understands care far better than one who was only warned.
What teachers tell us works
A few habits make the biggest difference. Let learners predict before they run a command, so every result is a small experiment. Celebrate error messages as information rather than failure. Pair confident learners with hesitant ones, and rotate who types. Connect every tool to something real: the firewall protects their home router too; grep is how you find a needle in a very large haystack.
Finally, end with a stage. Presenting to guests on the last day turns six days of learning into something a learner can explain to others, and explaining is where understanding settles. The certificate matters, but the presentation is what they remember.