Curriculum
Every week ends with something deployed.
We teach fewer tools, more deeply. By week twelve you will have deployed eleven projects, written about two thousand lines of tests and read more other people's code than most juniors see in a year.
Module map
Sort by length or project to see how the weeks stack up.
| Foundations | 3 | JavaScript, Git, CLI | Personal site and a command-line game |
|---|---|---|---|
| Front end | 4 | React, TypeScript, Vite | Team dashboard with live filtering |
| Back end | 2 | Node, Express, Postgres | REST API with auth and migrations |
| Capstone | 3 | Whatever the client needs | An MVP for a real Austin organisation |
A normal week
- 01
Monday: new concept, new pair
A morning lecture of ninety minutes, then pairing on the week's exercises until lunch.
- 02
Tuesday to Thursday: build
Project work with stand-ups, code reviews and one-to-one help from the instructor on duty.
- 03
Friday: deploy and demo
Ship to production, present to the cohort and write a retro about what you would change.