SESSION 6 · ~60M
Deploy & share
Deploy it, write a short launch note, and capture the lessons — the final loop that turns a build into durable learning.
The capstone closes with three steps: deploy it so others can use it, write a short launch note explaining it, and capture the lessons into your notes system. Each step consolidates what you've learned — the build isn't really finished until you've taught it.
The three close-out steps
- Deploy — push the static build and open the URL fresh, as a user would.
- Write a launch note — five lines: the problem, the tool, how to use it, one limitation, what's next.
- Capture lessons — move your prompt log and learnings into your notes system as reusable knowledge.
The launch note forces clarity. Compressing your work into five lines tests whether you actually understand it — if you can't explain it briefly, you don't fully grasp it yet. That compression is itself a learning act, not just a sharing one.
The protégé effect: explaining what you built deepens your own understanding. The launch note isn't documentation for others — it's the final study technique for you. Teaching, even to a small audience, is how learning locks in.
Move the lessons somewhere durable. Your prompt log, the gotchas, the prompts that worked — these belong in your notes system, not lost in a chat history. A captured lesson compounds; a lost one evaporates. This closing step is what makes the course's knowledge permanent.
TRY IT
Deploy your capstone and write its five-line launch note. Then create one note in your system capturing the single most useful prompt or lesson from the build. You have now shipped a real tool and encoded the learning to reuse forever.
CHECK YOUR UNDERSTANDING
What is the 'protégé effect' and how does it apply to the launch note?
What are the three close-out steps for the capstone?
What should a launch note contain, according to the module?
NOTEBOOKLM
Connect your notebook
Paste a NotebookLM share link to embed your notebook for this module.