Ship Week
One lab. One week. One demo day.
A weekly cadence where the community picks a lab, ships it, and demos what they built.
// How It Works
Community votes or maintainer picks the lab for the week. Get your environment ready and read the requirements.
Build, break things, fix them, and document everything. Share progress in Discord. Help others when stuck.
2-minute demos in Discord voice. Show what you built, what broke, and how you fixed it. No slides needed—just your terminal and repo.
// Demo Format (2 minutes)
Keep it real. Keep it short. We want to see what you shipped.
$ Quick walkthrough of your implementation
$ The decision that mattered most
$ The gnarliest bug or blocker you hit
$ Your solution or workaround
$ If you had more time, what would you improve?
// Ship Requirements
To get credit for shipping, you need these artifacts:
Repo Link
Public GitHub repo with your code
Demo or Screenshots
Proof that it actually works
Write-up
README with tradeoffs, what broke, and the fix
2 Resume Bullets
How you'd describe this on your resume
// Why Ship Week?
Weekly deadline keeps you shipping, not just learning
Learn from others' solutions and debugging approaches
Build 52 real projects a year with receipts
Practice explaining technical decisions under time pressure