Capstone
Design, build, and defend your system
Project design, build, demo, and templates as learning shortcuts. Being rewritten alongside the Safety chapter for the new course shape; existing cards are still reachable by direct URL.
After this chapter you can
→ Produce a project blueprint with users, data, risks, and MVP definition
→ Validate a working system through five structured test cases
→ Present a defensible architecture — not just a demo
11 n8n
Project design
28 n8n
Project studio I — design
Students need time to turn concepts into a concrete build plan. Projects that skip design spend the build week flailing — and "we'll figure it out as we go" is the most expensive sentence in software.
12 n8n
Project build
29 n8n
Project studio II — build and test
Systems improve through iteration, not first drafts. Expect the first working version to fail on realistic inputs — that's not a setback, that's the data you came here to collect.
13 n8n
Demo day
30 n8n
Final systems review and demo
Students should finish by defending design choices, not just showing a shiny output. A demo that only shows successes is a sales pitch; a demo that also names limits is a scientific contribution.
34 n8n
Explore templates as learning shortcuts
Fork, don't start from scratch. The fastest way to ship — and to learn what good looks like — is to clone a working template, read how it's built, and change one thing. Students who always start from scratch spend 80% of their time re-inventing things they could have inherited.