Module 1
From features to systems
Invariants, failure modes, and describing a product without listing tickets.
← All products
Self-paced course · Six chaptersInstant access
Software Engineer to Architect
Move from feature tickets to system design: boundaries, data, reliability, ADRs, and a capstone architecture proposal — with chapter slide decks.
What it is
A self-paced course that moves engineers from feature ownership to architecture practice — boundaries, data, reliability, ADRs, and a capstone proposal — with HTML/CSS chapter slides.
How it works
Pay once for library access. Work one chapter a week, complete exercises on a system you know, and finish with a reviewable architecture proposal.
Why it's worth it
You leave with ADRs and a proposal your team can debate — not a vague 'think bigger' pep talk.
Built for
Practitioners shipping work, not collecting certificates.
Each chapter ends with exercises. The capstone is a deliverable you can present or implement.
Engineers stepping into tech-lead or architect responsibilities.
Seniors who own cross-team surfaces and need clearer seams.
Staff-track engineers formalising trade-off communication.
Teams standardising ADRs and design reviews.
Curriculum
Six chapters. One architecture proposal.
Module 2
Boundaries and contracts
Seams where change rates differ — interfaces that outlive implementations.
Module 3
Data and consistency
Sources of truth, derived views, and idempotent writes as product choices.
Module 4
Reliability and operations
SLIs, degradation modes, and observability as architecture inputs.
Module 5
Decision records
ADRs that capture context, options, and consequences — not just diagrams.
Module 6
Capstone proposal
A reviewable architecture proposal with migration path and ADRs attached.
Chapters & slides
Visual decks for every chapter.
Preview the HTML/CSS teaching slides below. Buyers get the full decks in the library alongside written chapters.
Features ship. Systems endure.
Architecture starts when you stop asking 'how do I build this ticket' and start asking 'what must stay true when ten more tickets arrive'.
- Boundaries over folders
- Contracts over convenience
- Failure modes named early
What you get
Chapters, slides, and a deliverable.
Six chapters from systems thinking through reliability and ADRs.
HTML/CSS slide decks for teaching visuals in every chapter.
ADR templates and a capstone proposal outline.
Lifetime library access — updates included. Download as a zip.
Frequently asked
About the course.
- When does it start?
- Whenever you do. Pay once, get instant email access, and start chapter one today. No cohort dates.
- How long does it take?
- Most people finish in four to six weeks at one chapter per week — roughly 3–5 hours per week including exercises and the capstone.
- Is it live or self-paced?
- Self-paced. Written chapters plus HTML/CSS slide decks — no live sessions required.
- Who is this for?
- Mid and senior engineers who already ship features and want a durable practice for boundaries, data, reliability, and decisions.
- What does it cost?
- One-time purchase — see the pricing page for the current USD price. 14-day refund if you have not used the library.
Get access
Pay once. Start chapter one today.
After checkout you receive an email with a library link and access token. Work through chapters and slides at your own pace.