Software Design in the 21st Century
summary
Argues that disciplined refactoring (the red-green-refactor cycle, frequent local commits on green) yields an economic speedup not just cleaner code, and shows a real system: a static-site toolchain of ~20,000 lines feeding ~1,200 XML sources into a Ruby transformer class ~400 lines long orchestrated by a maker that emits deterministic HTML so end-to-end tests run in 1.5 minutes. Recommends preparatory refactoring, tiny steps, and domain knowledge to avoid dark patterns and privacy harms.
AI-written summary · about
chapters (20)
- 0:00Refactoring
- 7:40Preperation refactoring
- 8:36Adding a new feature
- 9:25Planned refactoring
- 10:44Largescale refactoring
- 12:19Why is refactoring important
- 12:58Cumulative function
- 15:00Moral argument
- 16:40Workflow refactoring
- 18:45Martin Fowlercom
- 21:07My approach
- 27:57Statistics
- 28:33One Way Transformation
- 29:20XML to HTML
- 34:03Bibliography Server
- 40:25Library Code Base
- 42:11Inheritance
- 50:31Dark Patterns
- 52:48Impact
- 56:24Software Rewrite
