Logic Line
Programming
The line everything else connects to. Students learn to think in steps, write real Python, and build tools that solve a problem they actually have. It is the skill that transfers to every other subject they study.
- Cadet
- Driver
- Engineer
- three terms, 12 weeks each
- Group size
- Six students per instructor, capped.
- Where to start
- Nobody is placed on paper. Your child comes to a free taster and we agree the level together.
- What to bring
- Nothing. We supply the machines, and every tool is free to keep using at home.
Three levels, one line.
A student joins where they are and moves up a level each term. Nobody repeats a year, and nobody starts from scratch twice.
Cadet
New to code · Usually 11–13
7 stops
For students who have never written a line of code. Week one assumes nothing.
A working program of their own — a quiz, a tool or a bot — that runs and does something useful.
- Python
- VS Code
- Git
- GitHub
- SQLite
Boarding
Week 1A program running in session one. Variables, input, output, and the moment the machine does what they said.
Decisions
Week 2Conditionals. Making a program that behaves differently depending on what it is told.
Repetition
Week 4Loops. Why a computer is extraordinarily good at the boring parts.
Collections
Week 6Lists and dictionaries. Holding more than one thing at once without losing track of it.
Functions
Week 8Naming a chunk of work and using it again. The idea the rest of programming is built on.
Debugging
Week 10Reading an error message instead of panicking at it — the single most useful habit in the course.
Ship It
Week 12A finished program they demo to the room, and take home working.
Driver
Building things that last · Usually 12–15
7 stops
For students who have finished Cadet, or who already tinker at home and can explain what a loop does.
A program with a real interface and real data — something a stranger can use without being told how.
- Python
- VS Code
- Git
- GitHub
- SQLite
Structure
Week 1Splitting a program across files. Why a thousand lines in one file eventually stops working.
Data In
Week 2Reading files and calling real APIs. Working with data they did not type themselves.
AI & Logic
Week 4Both linesBoth lines stop here. How a machine actually reaches a decision, where it gets things wrong, and how to check its work instead of trusting it.
Interfaces
Week 6Giving a program buttons instead of a blinking cursor, then watching someone else use it.
Storage
Week 8Saving state properly. Databases, without the jargon that usually comes with them.
Testing
Week 10Proving it works rather than hoping. Writing the test that catches your own mistake.
Ship It
Week 12Deployed somewhere real, with a link they can send to someone who wasn't in the room.
Engineer
Working like a professional · Usually 14–16
7 stops
For students who have finished Driver and can build something unaided. The term is mostly their own project.
A project they specified, built and released themselves, with the code public and readable on GitHub.
- Python
- VS Code
- Git
- GitHub
- SQLite
Specification
Week 1Deciding what to build — and, harder, what not to build. Scope is a skill.
Algorithms
Week 2Sorting, searching, and the first real answer to why one solution beats another.
Version Control
Week 4Git properly. Branches, history, and being able to undo a bad afternoon.
Working Together
Week 6Reading someone else's code and adding to it without breaking it.
Performance
Week 8Measuring before optimising, then making it genuinely fast.
Code Review
Week 10Giving and taking feedback on code without taking it personally.
Ship It
Week 12Public repository, a README a stranger can follow, and a release.
Or take the other line.
Plenty of students run both — one line this term, the other next. The AI & Logic block in the Driver term is the same lesson on either.
Try one session before you decide.
The taster is a full 90-minute session and it’s free. We’ll agree the right level together afterwards.