Module 1, Lesson 1
Why Architecture Matters: The Hidden Cost of Complexity
28 min · HD 1080p
Module 1 · Lesson 1 · 28 min · Updated March 2025
In this opening lesson, Dr. Vance dissects why software complexity compounds exponentially rather than linearly, and why ignoring architectural decisions early on leads to catastrophic rework costs. We examine three real-world post-mortems — one from Twitter, one from Monzo Bank, and one from an anonymous Fortune 500 — to understand the exact moment architectural debt became unserviceable.
You will walk away with a mental model for evaluating any system's "architectural load" and a vocabulary to articulate these concerns to both peers and leadership.
Notes for this lesson
Downloadable Resources
Questions from this lesson
Is the O(n²) complexity analogy based on Conway's Law? Would love to see a concrete formula.
Yes! It aligns with Dunbar's number applied to teams. I'll drop the full derivation in the resources doc.