Python 3
Advanced IntermediateModules, files, errors, clean notebooks. Not production microservices.
Live online worldwide · GCC evenings (GST/AST) · Engineered for the Few.
Worldwide · GST / AST
Ages 15–18
Ages 15–18 treat AI as engineering — measure errors, state limits honestly, and ship a demo a parent can try.
Class
1 : 4 · 4 children
Term
24 studios · 12 weeks
Weekend
Friday + Saturday
Length
75 minutes each
15–18s who want AI they can actually run and explain. A short diagnostic first. Gaps in Python are filled or we place into App Builders.
Not a mystery box. They train a small model, build a scoped vision demo, and finish a capstone with a system card — Friday and Saturday labs, four engineers, one mentor.
How the term runs
Fri & Sat · 18:45–20:00 · AST / GST · 75 minutes
60–90 minutes between studios · English · live online.
Friday
Lab: train, try, break, note what happened.
Saturday
Critique: where did that answer come from?
Ship
A parent can type, point a camera, or read the card.
Not a logo list. Each line is the level they reach by the end of the term — and what that means in practice.
Modules, files, errors, clean notebooks. Not production microservices.
Reproducible runs, clear variables, and plots they can explain.
Tables, splits, charts — say what a column means.
Train/test split, a classifier, metrics, confusion matrix.
Image as data; a safe demo UI with stated limits.
Repo hygiene, README, and a publishable model/system card.
At each stage the mentor helps them choose. By showcase night, three builds exist that the family can open.
Project 1
Studios 1–8
Spam/filter, simple predictor, or Data Detective
They ship: Notebook + small demo with data sheet and metrics
Project 2
Studios 9–12
Object Lens (vision) or a scoped gesture/posture demo
They ship: Safe demo + wrong-prediction gallery + intended-use note
Project 3 · Capstone
Studios 13–24
Notes chatbot, constrained agent, or Color Rover sim with logs
They ship: Repository, demo/walkthrough, system/model card, defence
How the twelve weeks move — foundations, builds, polish, showcase. Lesson-by-lesson teaching plans stay with the mentor.
AI as engineering, data quality, baselines, metrics, bias — then Project 1 ships.
Pixels to predictions, error galleries, and a demo that states what it must not be used for.
Sensing-to-action or tool boundaries, logging, and red-team evaluation.
Proposal, build, measure, write the card, rehearse, and showcase.
By the end of the term
Cold-start the project, show a metric, explain a wrong prediction, state intended use and refusal cases, and defend the work in twelve minutes.
Inside the studio
Studio format
Studio size
1 mentor · 4 engineers · seminar + lab in the same studio
Cadence
Friday + Saturday · 24 studios over 12 weeks · GST / AST
Language
English · technical writing parents and universities can read
Standard
If they cannot restart it and explain a failure, it is not finished
Craft in the room
Data & models
Clean a small dataset, train or fine-tune lightly, measure — no mystery “AI magic” buttons.
Vision & perception
Cameras, classifiers, and confidence they can plot — when the model is wrong, they say so.
Agents & tools
Pipelines that call tools, log steps, and stop safely — built to be audited, not demoed once.
Systems discipline
README, environment, logs, and a cold start. University-ready hygiene, not slide decks.
Mentors demand the why. Hype slides fail. A calm walkthrough of data, model, and failure modes is the only pass.
Open the live demos below. These are the kinds of builds in AI Engineers — games, sites, and tools a family can try on the call.
AI chatbot
Answers only from a notes pack — refuses when outside scope.
Number reader
Draw a digit; get a guess and a confidence number.
AI chatbot
Chat grounded in study notes — refuse homework it should not do.
Camera AI
Point a camera, get a label and confidence — admit when unsure.
Ready when you are
We’ll check AI Engineers is the right fit for their age and what they like to make.