Good Fences Make Good Neighbours
summary
Claim: modular boundaries must be chosen with a holistic sociotechnical view, not just code. Cites Accelerate that architecture beats automation for performance, quotes research showing ~30% faster incident resolution and a thought experiment claiming up to 20× optionality from recombinable modules. Recommends concrete techniques: look for natural seams (Michael Feathers), use information hiding (Parnas), event storming, DDD and Team Topologies, and iterate outside‑in with participatory workshops to avoid creating a distributed ball of mud.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:10Good Fences Make Good Neighbors
- 4:52Boundary Fiction
- 6:17Psychology
- 10:13Parallel work
- 22:04Social system
- 22:59Open system
- 27:26Factions
- 28:53David Panas
- 30:27YODA
- 32:39Topdown vs Outside
- 34:35Service Orientation
- 35:30Event Storming
- 36:34Free Book
- 37:20Emergence
- 38:35Complexity
- 40:24Holistic view
- 41:47Summary
related talks
59mGood Fences Make Good Neighbors
48mGood Fences Make Good Neighbours
52mGood Fences Make Good Neighbours
43mGood Fences Make Good Neighbours
41mUsing Boundary-Driven Development to beat code complexity
41mCultivating Architecture in an Agile World
31mModularity in open systems
44mBuilding resilient frontend architecture