Rakentamo
Three weeks, after which you have three provable pieces of work in a portfolio — not a certificate, but things somebody has read and responded to.
What you are committing to
- Three calendar weeks, a fixed start date. You work at your own pace, but the weeks move together.
- 8–12 hours a week: lessons, a build lab, the week’s Ship and the feedback.
- A crew of 2–4 who read your work every week — and whose work you read.
What you leave with is not a course certificate. It is three artefacts in your portfolio, each with its own narrative: what you built, what changed, what it proves about you. That link can go to a recruiter.
Three weeks
- W1
Greenfield: from prompting to spec-driven
Prompting → Spec-driven
- W2
Brownfield: from spec to loop
Spec-driven → Loop Engineering
- W3
Factories: discipline that scales
Loop Engineering → Factories
Week 2 branches by cohort: Builders take the discipline into existing code, Agent Builders build an agent. Week 3 is the same for both — a factory, running agents for the agents track.
Live sessions
Four Mondays. The sessions open the week — they are not mandatory, attendance is not tracked, and each one is recorded. The programme can be completed without attending any of them.
Kick-off and the week 1 start
Mon 31/08, 13:00–15:00 · 120 min
The arc of the programme, crews, the weekly rhythm — and starting the greenfield lab together. The longest session, because this is where you get going.
The link is added closer to the time.
Week 2 start
Mon 07/09, 13:00–14:00 · 60 min
What week 1 taught, and where the branch goes: brownfield or agents. Loop Engineering and the /goal lab walked through.
The link is added closer to the time.
Week 3 start
Mon 14/09, 13:00–14:00 · 60 min
Starting the factory week. The branches rejoin: both build a factory, the agents track one that runs agents.
The link is added closer to the time.
Retro and Q&A
Mon 21/09, 13:00–14:00 · 60 min
After the programme: what stuck, what goes in the portfolio, what comes next. Open for questions.
The link is added closer to the time.
The weekly rhythm
Ship
One provable artefact a week, with its evidence. Not a report — a demonstration.
React
You read at least two other Ships and give one structured response. This is the part that cannot be automated.
Pin
You write the week’s narrative and pin the work to your portfolio.
Deadlines are soft. A late Ship still counts and says so; a closed React window still accepts your response. If you get stuck, a mentor opens the week for you. Nobody is dropped from the programme for being late.
How you get in
By invitation (the usual way)
Most people arrive through Saranen: you get an email with a link to a named cohort. The link takes you straight in — you do not have to find the right cohort here. If you are expecting an invitation and it has not arrived, contact your Saranen adviser.
On your own
Rakentamo — Saranen, syyskuu 2026
Starts 31 August 2026 · Ends 22 September 2026
Week 2: brownfield — the process applied to existing code.