Technical Modeling as a Practice
summary
Asserts that Conway's Law and actor‑network thinking predict isomorphic structures across code, teams and orgs, shows a concrete case where multiple teams build a shared acceptance‑test framework that becomes a central god class then fragments when teams copy it into repos or build plug‑ins, cites repository analysis: 20% of devs make 80% of commits (and higher quality) across >1,000 projects, demonstrates small teams (2–6 people) and archival practices as practical remedies, and treats automated tests as a compensating memory for staff turnover.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 11:24Pareto Distribution
- 16:14Heroes
- 18:44What does this mean
- 20:49Cognitive limits constrain structure
- 22:02Galileo scaling law
- 23:32Social tension
- 25:51Internal differentiation in biology
- 26:23Feature teams
- 28:53Scaling down
- 29:59Scaling factor
- 30:42Twoperson teams
- 35:17Drawing the graph
- 36:17What can we do with this
- 38:13Dysfunction in organization
- 40:00Automated testing
- 41:37Dynamics
- 43:37Encapsulation
- 44:53Crosscutting Teams
related talks
43mSocio-Technical Modeling as a Practice
49mConway's Law: When Best Practices Are Not Enough
50mConway's Law: When Best Practices Are Not Enough
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
40mThe (too) many faces of architecture
58mMicroservices and the Inverse Conway Manoeuvre
47mMicroservices and the Inverse Conway Manoeuvre
01h 00mMicroservices and the Inverse Conway Manoeuvre