Continued Learning: The Beauty of Maintenance -
summary
Defines coupling precisely: A and B are coupled if changing A forces a change to B and shows a concrete fix when a parameter name change ripples through seven services using a parallel change pattern (deploy duplicate field c, switch readers, remove b). Notes a Facebook incident where a backup saturates a rack switch and couples unrelated services, and a Gusto constraint where tax rules force brittle code. Recommends separate structure and behavior PRs and experiments with a 3x model: explore expand extract to keep changes small and reversible.
AI-written summary · about
chapters (11)
- 0:00Introduction and personal journey
- 3:57Public speaking and performance anxiety
- 9:14Coupling and cohesion fundamentals
- 19:10Cost of change and coupling impact
- 24:34Subtle coupling and system complexity
- 30:45Trade-offs in software design
- 35:45Domain complexity and responsibility
- 41:46Behavior vs. structure changes
- 48:04Separating behavior and structure PRs
- 50:32Feedback loops and waterfall critique
- 53:21DDD's role in feedback culture
related talks
48mBalancing Coupling in Software Design
51mBalancing Coupling in Software Design
41mUncoupling
01h 01mBalancing Coupling in Software Design
51mHiding The Lead: Coupling, Cohesion, and Microservices-Style
58mA Practical Guide to Loose Coupling
41mConnascence, beyond Coupling and Cohesion
44mDependencies; Devil or Darling?