Through the Looking Glass
summary
Conway’s law becomes a dynamic claim: architecture and org structure undergo a continuous homomorphic fitness transformation with measurable drift and sudden homomorphic disjunctions. Near-decomposability shows teams talk more inside than between, causing multi‑tempo effects — CI cadence matters (longest‑living branch predicts pain; frequent checkins avoid merge party spikes). Examples: Unix pipes and platform granularity shift complexity between users and infra. The practical takeaway is joint optimization of social and technical constraints using fitness curves and temporality-aware interfaces.
AI-written summary · about
chapters (18)
- 0:00Introduction and context
- 1:50Context as constraint regime
- 3:15Modularity in different contexts
- 5:45Reinterpreting Conway's law
- 8:57Hierarchy and control systems
- 12:51Homorphism and system structure
- 15:58Homorphic fitness and drift
- 20:58Herbert Simon's organizational design
- 29:52Near decomposability explained
- 37:13Heat dissipation metaphor
- 43:47Structuring information for release
- 46:55Sociotechnical dynamic interactions
- 48:16Optimization and trade-offs
- 51:05Requisite variety and complexity
- 53:11Unix design principles example
- 56:06Granularity and platform design
- 58:39Applying architectural qualities to organizations
- 1:00:46Conclusion and key takeaways
related talks
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
01mConway's Law
45mConway's Law: when best practices aren't enough
24mThe (too) Many Faces of Architecture
49mConway's Law: When Best Practices Are Not Enough
41mHow I Finally Stopped Worrying & Learnt to Love Conway’s Law
50mConway's Law: When Best Practices Are Not Enough
58mMicroservices and the Inverse Conway Manoeuvre