Architecture Blindspots, Biases, and Blunders: Avoiding Common Pitfalls in System Design
summary
Argues that cognitive traps cause concrete architectural failures: reusing an old feature flags toggle and a manual shell-script deployment left one node out of eight running retired code, the SMARS router floods markets (one minute to detection, shutdown at 28 minutes) and generates losses peaking at $10 million per minute until bankruptcy; microservices are flagged as overprescribed without domain‑aligned teams, DDD, CI/CD, infra‑as‑code and automation, so migrations take years and often fail when organizational maturity doesn’t match the architecture.
AI-written summary · about
chapters (9)
- 0:00Introduction to holistic architecture
- 1:46Architectural blind spots explained
- 3:55Biases in system design
- 7:29Night Capital's $10M blunder
- 25:49My microservices failure story
- 37:11Non-architectural constraints matter
- 44:18What is modern architecture?
- 47:49Overengineering and context
- 54:39Closing and Q&A
related talks
44mCognitive Biases Driven Architecture?
34mCognitive Biases and Agile Architecture
45mThe Unbearable Weight of Architecture
49mWhy software architects fail: and what to do about it
38mFallacies of Software Development
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
44mDeliberate Architecture
56mBeyond the Known Knowns