Inside a term
Twelve sessions, one shipped product.
The question we are asked most is what actually happens in the room. Here is a full Engineering Studio term, session by session. Every student walks out with a working product on a live URL and the ability to explain how it was built.
Session 01What the machine is actually doing. First program, first bug, first fix.
Session 02Thinking in steps — logic, loops, and breaking a problem into parts.
Session 03Build a web page that is genuinely yours, not a template.
Session 04Make it interactive. Forms, state, and what happens on a click.
Session 05Talking to an API — your code calls somebody else's and gets an answer back.
Session 06First AI feature. A real model doing real work inside your own app.
Session 07Computer vision. The camera sees something and the program reacts.
Session 08Data and databases — where the work lives when the browser closes.
Session 09GitHub. Version control, and why you will be grateful for it later.
Session 10Testing — finding the problem before somebody else does.
Session 11Deployment. It goes live, on a real URL, that a parent can open.
Session 12Demo day. The student presents, and the room is allowed to ask hard questions.
Sample arc for one studio. The other six run the same way — short cycles, a finished artefact, and a demo the student presents themselves.
