Good Fences Make Good Neighbours
summary
Argues that modularity succeeds only when treated as a sociotechnical system and not just code, claiming a systems thinking approach that combines business capability mapping and event storming with patterns from Domain‑Driven Design, Team Topologies and Conway’s Law. Uses experience extracting parts from a proud monolith to show emergent refactoring often breaks hidden ties. Cites DORA evidence that loosely coupled architecture drives performance more than tooling, and recommends continuous synthesis (outside‑in) plus bottom‑up learning.
AI-written summary · about
chapters (14)
- 0:00Start
- 9:08Intrinsic Cognitive Load
- 9:36Scale Scaling and Organization
- 19:05Definition of a System
- 21:32Reductionism
- 27:30Open Systems
- 29:37Streamlined Teams
- 35:14Business Capability Mapping
- 37:14Business Capability Map
- 37:57Domain Driven Design
- 41:21Independent Service Heuristics
- 41:44System Thinking
- 42:13Open System Theory
- 45:07Social Technical Congruence
related talks
48mGood Fences Make Good Neighbours
43mGood Fences Make Good Neighbours
46mGood Fences Make Good Neighbours
31mModularity in open systems
48mModularization — It Was Supposed to Be Beautiful but Turned Out as Usual :(
01mMark Richards at DDD Europe
01mModularization: Foundation of Microservices and Monoliths
49mRealizing Domain Design Through Architectural Modularity ...