The Art of Being Lazy
summary
Advocates treating “laziness” as automation and simplification by programming for humans, asking the right questions, and avoiding premature features. Uses concrete failures—copy‑paste bugs repeated across six pages, code rewritten up to fourteen times, and switching to Picasso for Android image loading—to motivate applying SOLID principles (single responsibility, interfaces, dependency injection) and building small, testable modules so changes deploy quickly and maintenance costs fall.
AI-written summary · about
chapters (21)
- 0:00Concept of laziness
- 1:27Laziness as efficiency
- 4:26Laziness in programming
- 6:22Pride in functional code
- 7:51Programming for humans
- 10:23Code simplicity
- 12:11Simplicity since the 60s
- 14:51Avoid premature work
- 17:28Unnecessary dependencies
- 19:45Copy-paste code
- 21:55Library copy issues
- 23:46Design patterns and repetition
- 27:39Flexible design
- 29:47SOLID principles
- 31:15Single responsibility
- 32:42Liskov substitution
- 34:36Interface segregation
- 36:53Dependency inversion
- 38:42Dependency injection
- 41:19Lazy programmer tools
- 43:59Conclusion
