Honest Take — Before You Begin
Ship something. Not a todo app. Not a counter. Not a clone of an app that already exists. Build something that solves a real problem you actually have. The difference between a po…
Synthesize everything from Modules 0-7 into substantial, portfolio-worthy projects that demonstrate full-stack JavaScript mastery. Each project should be something you would be proud to show in an interview or open-source. These capstones are the JavaScript equivalent of building a Rails gem or a complete Rails application. Capstone A (SaaS) is what you do in Rails daily — but now you can compare the full-stack JS experience. Capstone B (component library) is like building a ViewComponent library but for the React ecosystem. Capstone C (collaborative tool) pushes beyond what Rails typically handles (real-time conflict resolution). Capstone D (CLI tool) is like building a gem with a CLI but in the Node ecosystem.
This course unlocks once you've finished its prerequisite. Open prerequisite →
Ship something. Not a todo app. Not a counter. Not a clone of an app that already exists. Build something that solves a real problem you actually have. The difference between a po…
Work through each item before the checkpoint.
A complete SaaS app — multi-tenant workspaces, real-time features, Stripe, email, an admin dashboard — built from an empty (but sharp-tooled) starter. CI checks completeness; your…
Ten-plus reusable components, published to npm — typed, tested, documented in Storybook, accessible, and tree-shakeable. The starter ships one exemplar component (Button) with its…
A collaborative whiteboard, editor, or kanban — real-time sync, conflict resolution, offline support, presence. This is the hardest capstone: the difficulty is in the sync design,…
A CLI tool other developers would actually install: interactive prompts, file transforms, a plugin system on dynamic imports, published to npm. The starter ships one working comma…
6 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.