Is Beauty Only Skin Deep?
summary
Claims that clean architecture buys back engineers' attention and shows it with a concrete JavaScript example: a Stripe order webhook that must do three things (validate, update inventory, email customer and post to Slack) is refactored from a tangled 15-line blob into explicit steps so intent is obvious. Adds observability so on-call incidents surface the failing email via logs, and demonstrates adaptability by adding SMS through the existing notifier class with no collateral changes. Key checks are intent visible, observe behavior, and localized changes.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:55Introduction
- 3:17Two identical houses analogy
- 8:37Bad code and impact
- 10:19Code intent and readability
- 12:46Observability and debugging
- 14:50Adaptability and change
- 17:00Beauty beyond code
- 18:27Q&A
related talks
42mStratified design and functional architecture
41mInside Software Architecture - Where the Bodies are Buried
01h 01mArchitecture: The Stuff That's Hard to Change
23mClean Architecture: A Twelve Months Journey to Clarity
01h 01mDesign Principles for Better FrontEnd Code
50mIntentional Code - Minimalism in a World of Dogmatic Design
21m[Eng Sub]if (extensible design) return "work life balance"
44mBuilding resilient frontend architecture
