COHORT 14 - STARTS 6 OCTOBER

Sixteen weeks.
Then you are employable.

Full-time, in one cohort, with the same twenty-four people the whole way through. No self-paced option, because the people who finish are the ones who cannot quietly stop.
16
Weeks
Full-time, Monday to Friday
24
Seats
Nine already taken
6
Projects
All of them shipped, none of them toys
0
Prior experience
Cohort 13 had a chef and a nurse

A week in the cohort

The same shape every week, so the work is the only thing that changes.
  1. Monday 09.30

    Brief

    The week's project, read aloud and argued over.

  2. Tuesday - Thursday

    Build

    Pairs, rotating daily. Mentors on the floor until 18.00.

  3. Wednesday 14.00

    Code review

    Somebody else reads your code, and you read theirs.

  4. Friday 11.00

    Demo

    It runs in front of the room, or it did not ship.

  5. Friday 15.00

    Retro

    What slowed you down, written down, fixed by Monday.

The six things you build

All of them go on a public repository with your name on it.
Nothing here is a tutorial you follow. Every brief is deliberately underspecified.
WeekProjectStackAssessed on
2-3A command-line toolPython, argparseDoes it handle bad input
4-6A REST API with authPython, PostgresIs it safe to deploy
7-8A front end for that APIJavaScript, no frameworkDoes it work without JS
9-11The same, in a frameworkReact, TypeScriptCan somebody else read it
12-14A team projectChosen by the teamDid you use version control properly
15-16Your ownWhatever you argue forDid you finish it

Where the time goes

Measured on cohort 13, averaged over the sixteen weeks.
Writing code 58%
Roughly 23 hours a week
Reading somebody else's code 17%
The skill nobody teaches
Lectures 12%
Short, and recorded
One-to-one review 8%
Weekly, with a mentor
Interview practice 5%
Every week from week nine

Cohort 13, one year on

Twenty-four started, twenty-one finished, and here is all of it.
The last two rows are on this page on purpose. A school that only publishes its wins is telling you about its marketing, not its teaching.
OutcomePeopleMedian timeMedian salary
Hired as a developer1611 weeks38,000
Hired in a related role38 weeks31,000
Still looking at 12 months2--
Did not finish the course3--

Short courses, if sixteen weeks is too much

Live from the catalogue.
I was a nurse in week one and shipping an API in week six. Nobody made it easy - they made it clear what the next hard thing was, every single Monday.
Priya, cohort 13Now a backend developer, eleven weeks after finishing

The awkward questions

Can I work while doing it?
No, and we will talk you out of trying. It is thirty-eight scheduled hours a week plus whatever you need on top.
Is there a payment plan?
Yes, over twelve months at no interest. There is no income-share agreement and there never will be - they are a bad deal dressed as a kindness.
What if I fall behind?
Weeks four and ten have catch-up days built in. If you are still behind after week ten we will tell you honestly whether to continue.
Do you guarantee a job?
No. Nobody can, and the ones who say they do are relying on you not reading the conditions.
What happened to the three who did not finish?
One had a family emergency and is joining cohort 15. Two decided it was not for them, in weeks two and five, and were refunded in full.

Applications close 19 September

A short written exercise and a conversation. No whiteboard, no trick questions.