Evolving Code Through Accretion
summary
Argues for evolving code by accretion: add new functions or namespaces instead of changing or deleting existing ones, so libraries and apps can coexist (example: wrapping a Fulcro component macro to always use hooks to avoid global breakage). Recommends using specs to parse macro syntax, creating macro-based DOM optimizations only when measured, preferring open maps and the end map pattern for passing environment, and naming with qualified keywords to give semantic context and avoid surprising breakages.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:56Avoid app-level configs
- 5:04Prefer accretion over breakage
- 11:28Sustainable software evolution
- 13:14Macros best practices
- 18:52Optimization with macros
- 21:41Building for extension
- 26:40End map pattern
- 32:40Let the end flow
- 33:01Final thoughts
