Net Positive Development
summary
Argues that network science explains why code, teams and organizations behave the same way and gives concrete rules: communication costs grow as n squared vs n so keep teams small, cognitive limits cluster people at about Dunbar ~150, and many metrics follow a power law so roughly 80% of change concentrates in 20% of files and a few contributors. Recommends two‑person pairing, targeting refactoring to hotspots, and using microservices to align code boundaries with small teams.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:38Net Positive Development
- 8:16Complexity
- 10:28Scaling Law
- 13:32Dunbars Number
- 14:45Brooks Law
- 16:15Graph Theory
- 19:16Managers vs Developers
- 21:21Tension between N and N
- 22:22Power Law Networks
- 24:34Income Distribution
- 24:59Pareto Distribution
- 26:15Network Science
- 26:42Method Size
- 27:55Refactoring
- 28:53Why Software Projects Need Heroes
- 32:05The Chief Programmer Team
- 33:25Cognitive Limits
- 33:47Explicit Complexity
- 34:48Cognitive Load
- 35:50Single Person Teams
- 36:18Two Person Teams
- 39:42Software Development
- 40:30Thank you
- 41:50Myth or Reality
- 43:04Measuring Positiveness
- 44:35Building Compliance
- 45:14People Becoming
- 46:05Language Choice
- 47:36Teaching in Software
related talks
53mScaling Agile: The Small-is-Beautiful of Hubs
34mCode as Culture How Organization Shapes Your Code
49mSoftware Architecture, Team Topologies & Complexity Science
47mMicroservices and the Inverse Conway Manoeuvre
53mKeynote - Software Architecture, Team Topologies and Complexity Science
39mTeam Topologies, Software Architecture & Complexity
51mTech-enabled Network of Teams
46mLeading Distributed Teams