🏆 The Capstone — Build Something Real
What this is: the final project of the course. You’ll pick one track, spend 10–20 hours over 2–4 weeks, and finish with something real — made by you, finished by you, showable to anyone.
Why it matters: everything you’ve learned so far lives in your head. The capstone moves it into the world.
🧠 Why a capstone?
There’s a difference between these two sentences:
“I took a course about software engineering.”
“Look what I made.”
The first is a claim. The second is proof. Module 19 was blunt about it: employers, collaborators, and (most importantly) you believe finished things, not certificates. A capstone converts knowledge into evidence — a link you can send, a page you can show, a story you can tell in an interview: what you built, where you got stuck, how you got unstuck.
And there’s a quieter reason. Somewhere around Module 05 you may have started to suspect you could actually do this. The capstone is where you find out that you were right.
🗺️ How it works
Pick one track below. (Finished one and want another? Wonderful — but one at a time, no rush, and the second one counts double for bragging.) Each track gives you:
- Milestones — the work, broken into steps small enough to finish in one sitting.
- A definition of done — a checklist that says exactly when you’re finished, so “done” is a fact, not a feeling.
- A “show it off” step — because a capstone shown to zero humans is only half finished.
| Track | In one sentence | Best if you… |
|---|---|---|
| 🌐 Track A — Personal Website | Build and publish a real multi-page website, live on the internet | loved Modules 08 and 17; want a public link with your name on it |
| 📋 Track B — Be the PM | Run a full product cycle — research, plan, and pitch — without writing code | loved Modules 07 and 18; aim at product/coordination roles |
| 🤖 Track C — Automate Your Life | Write a small Python program that does a real chore you hate | loved Modules 04 and 05; want to prove the coding stuck |
📏 The rules
1. Small is beautiful. A finished-small project beats an abandoned-big one — every time, in every way. The graveyard of learning-to-code is full of half-built grand visions. Your capstone should feel slightly too modest when you plan it. That’s the correct size.
2. Use everything from the course. This is the point of a capstone — the tools stop being lessons and start being your tools:
- Git for version history (Module 08) — commit as you go; your history is part of the deliverable.
- User stories to plan (Module 07) — before building anything, write who needs what and why.
- A test plan before “shipping” (Module 09) — try to break your own work before showing it.
- The Glossary when a word goes blurry — that’s what it’s for.
3. Budget honestly: 10–20 hours over 2–4 weeks. In sessions of 1–2 hours. Put the sessions in your calendar now — the Lab 19 plan has a slot waiting for exactly this.
4. Getting stuck is part of the project, not a failure of it. Module 19 called it the learning loop, and the loop requires the stuck part. When it happens, run the protocol:
🪜 The getting-unstuck protocol
Work down this ladder, in order. Most problems die on the first two rungs.
- Reread. The instruction, the error message, your own code — slowly, aloud if nobody’s watching. Half of all bugs are a mismatch between what you wrote and what you think you wrote.
- Search the exact error in quotes. Copy the exact message into a search engine, in quotation marks. Someone has hit your error before. Their thread is waiting.
- Rubber duck. Explain the problem out loud, line by line, to a duck, a pet, or a patient spouse (Module 09 taught you why this absurd trick works — explaining forces the fuzzy part into the open).
- Ask a community, with a good question. The one you joined in Lab 19. Include: what you’re trying to do, what you expected, what happened instead (exact error), and what you already tried. Questions shaped like that get answers within hours — and writing one often reveals the answer before you hit post.
⚠️ Watch out: the ladder has a hidden fifth rung — walk away for a day. It feels like quitting. It isn’t. Brains debug in the background; the number of bugs solved in the shower is not a joke, it’s a documented phenomenon.
🚀 Pick your track
- 🌐 Track A — Ship your corner of the internet
- 📋 Track B — Run a real product cycle
- 🤖 Track C — Make the machine do a chore you hate
And when you finish — and you will — add your name to the Showcase. Adding it is itself a final Git exercise, and your entry becomes part of this course for every learner after you.
Go build your proof. 🛠️