Understand it first. Then build with it.
Every course here is built on the same method, and it is not the one most bootcamps use. It is slower through the first weeks, and it is why people finish able to work on things nobody showed them.
Most people are taught the syntax and never given the idea.
That is why so many people finish a course able to rebuild the project they were shown and nothing else. They were given the steps without the reason, so the moment the problem changes shape there is nothing to reason from.
We teach the reason first. It feels slower for a fortnight and then it compounds, because every new thing you meet attaches to something you already understand.
Four rules we don't bend.
They shape how every session is written, how exercises are pitched, and what we refuse to do to keep a syllabus looking impressive.
The model before the syntax
Syntax is the cheapest part of programming and the first thing you forget. We spend the time on the idea underneath — what the machine is actually doing — because that is what survives, and what lets you pick up a language nobody taught you.
One idea at a time
Chunk-based teaching: a session introduces a single concept, uses it, and stops. Four ideas in an hour feels productive and teaches none of them, because there is no room left to be usefully confused about any one of them.
Being stuck is the lesson
Exercises are pitched just past what you already know, which means you will get stuck. That is the part where the learning happens, so sessions leave room to be wrong out loud before the answer turns up.
You should be able to explain it
Code runs by accident all the time, so the test of understanding is never that it works. It is whether you can say why it works. Every module ends with something you could defend to another person.
Three parts, every time.
The same shape across all 13 courses, because the order is the point: the idea, then your attempt, then something to measure it against.
A mental model
The session opens with the idea in plain language, before a line of code appears — usually as a picture of what the machine is doing, or an analogy that holds up under pressure.
Syntax attached to an idea is memorable. Syntax attached to nothing is a list.
An exercise brief
A focused task you cannot finish by pattern-matching the example. It forces you to use the concept, which is how you find out whether you actually hold it.
Reading code you understand feels identical to reading code you don't.
A model answer
A worked solution written the way we would write it, with the reasoning left in. It is there to compare against yours, not to replace the attempt.
Nobody learns what good looks like from a blank page and a passing test.
A week is a pace, not a deadline.
Every course states a length — eight weeks, twelve weeks. That is what it takes at the hours the course asks for, not a term you have to keep up with. You start the day you are ready, and you move at your own pace.
Give it double the hours and you will finish in half the time. Give it less and it takes longer. The order of the material does not change, and neither does the teaching.
What you won't find here.
A teaching method is defined as much by what it leaves out. These are the four things we have decided not to do, and why.
Slides, read aloud
If a session could have been a document, it should have been a document. Time together is for working through the hard part, not narrating bullet points at you.
Copy-along tutorials
Typing what somebody else typed produces a working app and no transferable skill. You will build things here that you have to think your way through.
Twelve tools in six weeks
A tour of frameworks looks impressive on a syllabus and leaves you unable to use any of them. We go slower, over fewer things, deliberately.
Frameworks before foundations
React before JavaScript, or a CSS framework before layout, produces developers who are fluent right up until something breaks. The course order is not an accident.
Pick a track and see the outline.
Every course page opens with the one idea it exists to teach, then what you need to know and have before day one.
Explore the coursesIt is how the studio works too.
Understand before you build is not only a teaching method here — it is eleven steps of system design before any client project gets written.
See how we build