Writing Code That Lasts Forever
summary
Argues for concrete practices to keep code maintainable: use branch by abstraction (example: Android Pie biometric enum with toggleable fingerprint vs iris paths, rolled out via Cash App admin dashboard to 1–5% buckets), run predictable release trains (Square ships servers daily and mobile every two weeks), invest in infra like gRPC (roughly 80 hours setup then cheap endpoints), separate value objects, service objects and glue, pull policies into testable classes, finish migrations and celebrate completion.
AI-written summary · about
chapters (15)
- 0:00Introduction to lasting code
- 1:54Incentives and team values
- 2:56Incremental changes and branching
- 8:29Learning organizations and feedback
- 10:34Infrastructure investments and demand
- 14:41Knowing your problem domain
- 15:44Modeling and stakeholders
- 19:14Value objects and service objects
- 22:42Writing and naming in code
- 24:07Less code and type systems
- 26:13Organizing by feature
- 27:58Building blocks and composability
- 28:19Policy and precedence in logic
- 32:50Finish transitions and celebrate
- 37:25Summary and closing
related talks
28mWhat Handcrafted Servers Taught Us About Handcrafted Code
47mPrioritization, Refactoring, and Keeping You Codebase Healthy
47mHow To Build Future Proofed Applications
25mBest Practices for Writing Clean and Maintainable Codes
57mCore Software Design Principles for Programmers
11mDo You Want to Take This Code With You into the Future?
01h 01mFixing the Ultimate Legacy System: You
01h 01mGuide to Destroying Codebases the Demise of Clever Code