Keynote: Growing Old
summary
Claim: software lasts when it’s born small, rebuilt often and encapsulated behind stupidly simple interfaces. Examples: Haskell service that outperforms rewrites but later fails to compile because Cabal changes; an immutable deployment rule replacing nodes constantly to keep uptime under an hour; use of Spot Instances and Chaos Monkey style faults to force recoverability; metric shift from MTBF to MTTR; testing framed as coupling not safety. Practical takeaway: code is liability, interfaces and replaceability are the asset.
AI-written summary · about
chapters (18)
- 0:00The state of Ruby and legacy
- 2:57Redefining legacy software
- 6:03Artistic influence on software
- 8:40The challenges of development
- 10:41Learning from past systems
- 15:02Building systems to survive
- 19:27The biological metaphor
- 23:08Regeneration and components
- 26:46Encapsulation and small units
- 30:29The role of code vs system
- 33:50Infrastructure as a system
- 36:06Immutability and side effects
- 38:29Simple system communication
- 40:56Heterogeneous development
- 42:50Testing and failure mindset
- 45:24Active regulation of systems
- 48:01Decoupling for the future
- 50:18A vision for Ruby's future
