Good Fences Make Good Neighbors
summary
Claim: modularity only works when boundaries reflect business goals, communication patterns and people, not just code. Advocates a systems‑thinking method that combines social-technical systems analysis with top‑down synthesis plus bottom‑up emergence (DDD, event storming, information hiding). Recommends organizing semi-autonomous teams that own whole tasks and data to reduce cross-team coordination; cites research showing improved incident resolution of about 32% when social and technical structure align. Offers practical heuristics (natural seams, business capabilities, Team Topologies) to iterate boundaries.
AI-written summary · about
chapters (31)
- 0:00Intro
- 4:30Fences Make Good Neighbors
- 6:44The Usual Fiction
- 8:06Cross Discipline
- 11:22Modularity
- 14:13Time to market
- 15:16Mud
- 16:46Book
- 20:10Experimentation
- 21:00Complexity
- 22:27Physics
- 25:47System Thinking
- 29:07Parts Change
- 30:35Russell Lake
- 32:02A Prime of System Thinking
- 32:41Different Types of Systems
- 35:10Open System Thinking
- 36:01Russel Lacov
- 37:31Reductionism
- 39:28Boundaries
- 40:19Social System
- 41:49Modularisation
- 44:08Change frequently
- 46:18Outside in view
- 48:19Business capabilities
- 50:30Main Dream Design
- 52:30Windstorming
- 54:08Free book
- 54:33Take a bigger picture
- 56:00Analysis and synthesis
- 57:01Conclusion
related talks
43mGood Fences Make Good Neighbours
46mGood Fences Make Good Neighbours
01mMark Richards at DDD Europe
41mUsing Boundary-Driven Development to beat code complexity
43mAdaptive Socio-Technical Systems with Architecture for Flow
44mDependencies; Devil or Darling?
46mMeet The Social Side of Your Architecture
26mRedefining collaboration norms as your company grows