Week 26 · Season 7 · Alive
Converged
You can review FRIDAY's whole design, draw it on a whiteboard, price every part honestly, demo it to strangers, defend your choices to a tough reviewer, and choose what comes next.
This week
- One product, not thirteen: a design review
- Draw it on the whiteboard
- Price the whole machine
- Demo it, defend it
- Converged: what you are now, and what next
- Go deeper: the case study, the interview, the next maps
How you learn
Trace one request through every part, draw FRIDAY from memory with labelled arrows, and price every part per month and per good answer, before you change a line of code.
What you build
Project 7 and the final boss: the public demo. FRIDAY works for strangers on seeded data, behind one front door, with a spend cap and limits per visitor, a system diagram, a cost sheet, a recorded walkthrough and a case study you defend against tough questions.
Stretch: Mentor a beginner through Season 1, and publish your case study with FRIDAY's real numbers.
What you ship
Project 7: The public demo. FRIDAY live for strangers, with a system diagram, a cost sheet and a demo you can defend.
- A live public demo link on seeded data, with a spend cap, and a recorded walkthrough
- A context diagram, a system diagram and a cost sheet
- A case study with a receipt for every number, and your answers to real questions
Lessons
- One product, not thirteen
After this deck you can trace a request path through FRIDAY's parts, run a design review that finds every single point of failure, and decide what to keep, merge and park before a feature freeze.
- Draw it on the whiteboard
After this deck you can draw FRIDAY as a system diagram with labelled arrows, open any review with a context diagram, draw a dashed line where trust changes, and find the planted mistakes in someone else's drawing.
- Price the whole machine
After this deck you can put a monthly price on every box, split fixed from variable costs, work out the cost per success, and set a spend cap before strangers arrive.
- Demo it, defend it
After this deck you can write a five-minute demo script that leads with the problem, prepare seeded data and a backup plan so a broken demo stays calm, and defend a trade-off with a number and what would change your mind.
- Converged
After this deck you can say what converged means for a model and for you, turn everything you built into a portfolio of receipts, and choose your next road, including teaching someone else.
- Go deeper: the case study, the interview, the maps
After this deck you can write a case study where every claim has a receipt and an interval, run an interview-style system design with napkin maths and Little's law, and pick your next learning path on purpose.
Labs
Python in the browser, next to the lessons.
Weekend build
- Project 7: Project 7 + final boss: the public demo
FRIDAY, live for strangers: one front door, a system diagram, a cost sheet with a spend cap, a case study with receipts, and a demo you can defend.
Skills you prove
- Translate
- Explain a technical trade-off to a non-technical decision-maker
Free links for this week
Hand-picked official docs, papers and talks.
- The C4 model: system context diagrams · docs
- OWASP Threat Modeling Cheat Sheet · docs
- The System Design Primer · repo
- swyx: Learn in public · post
- Stanford CS336 (deep reference) · course
- How to Scale Your Model · course
- Anthropic Fellows / alignment · program
- MATS · program
- EleutherAI · program