Build Week: why game jams are still the best place to learn to ship
Tools have made building cheap. Finishing is still hard, and forty-eight hours with a deadline is the fastest way we know to practise it.
Anyone can start a project now. The scaffolding writes itself, the deploy is one command, and the first screen appears in minutes. What has not changed is the part after that: deciding what to cut.
The deadline is the curriculum
A jam compresses the whole life of a project into a weekend. You scope, build, discover you scoped wrong, cut, and ship — usually in that order, usually twice.
Nobody remembers the feature they cut on Saturday night. Everybody remembers shipping on Sunday.
What we saw at this year's Build Week
2025 | 2026 | |
|---|---|---|
Teams | 412 | 655 |
Projects shipped | 61% | 74% |
First-time participants | 38% | 52% |
How to run one at your company
Pick a theme on Friday, not before.
Ban slide decks from the demos.
Give a prize for the best cut, not just the best project.
# buildweek.yml
theme: "small tools for big teams"
duration_hours: 48
demo_minutes: 3
prizes:
- best_ship
- best_cut