'Writing code that lasts'...or writing code you won't hate tomorrow
summary
Code ages and must be easy to change so it survives: testing gives design confidence, PSR-7 middleware moves validation out of controllers, queues handle slow image processing, and Composer encourages reuse. Follow Object Calisthenics (10 exercises) — one indent per method, no else, wrap primitives, small classes, few instance variables — and prefer tell‑don’t‑ask over getters. Doctrine’s unit of work is cited as a performance tradeoff; these practices aim to make refactors cheap.
AI-written summary · about
chapters (42)
- 0:00Intro
- 1:22Past Rafael
- 2:10What was I thinking
- 2:24Rewrite everything
- 2:59Shipping
- 3:47Tacoma Narrows Bridge
- 4:28More wind
- 5:00Your server is screaming
- 5:42We need to find a balance
- 5:59Code has an expiration date
- 6:38Code evolves
- 6:59PHP evolves
- 7:36Evolve as a developer
- 8:33Comprehension
- 8:55Bad design
- 9:20Bad specs
- 10:09NIH
- 10:19The Great German Art
- 11:58Improve Code
- 14:28Testing
- 15:20No testing
- 15:55Good design concepts
- 16:11Solid and stupid
- 17:25Design patterns
- 19:11Maindriven design
- 19:44Modular architectures
- 20:34Package managers
- 21:14Readability
- 22:33Object Aesthetics
- 22:44Object calisthenics
- 23:49Rules
- 25:10Code examples
- 28:29Breakpoints and exit points
- 29:04Wrapping primitives
- 31:48One arrow per line
- 32:47Dont abbreviate
- 34:37Keeping classes small
- 35:13Instance variables
- 36:43Use firstclass collections
- 37:49Immutability
- 39:59Documentation
- 42:46Evolution
