Software takes the shape of the people who build it.
Your architecture will mirror your org chart. Your team's communication patterns will become your codebase's structure. You cannot design your way out of a people problem. The hard constraints are not technical. They're human.
Reading path
Conway's Law
Understanding the fundamental principle that software systems mirror the communication structure of the organizations that build them
- leadership-fundamentals
5 min read
Architecture Is A Team Decision
Why software architecture decisions impact the entire team and how different architectural patterns affect development efficiency
- leadership-practices
- engineering-fundamentals
6 min read
Microservice Architecture
Why microservices solve team coordination problems, not technical problems, and why most organizations would be better served by monoliths
- leadership-fundamentals
- engineering-fundamentals
6 min read
Brooks' Law
Understanding the counterintuitive principle that adding more developers to a delayed software project often increases the delay
- leadership-fundamentals
5 min read
Law of Diffusion
How innovations spread through organizations and why technical excellence alone doesn't guarantee adoption
- leadership-fundamentals
5 min read
Ubiquitous Language
How establishing a shared vocabulary between business and development teams eliminates translation overhead and improves software quality
- engineering-fundamentals
- leadership-fundamentals
5 min read
Shared Maps Beat Diverse Maps for Execution
Why teams with aligned mental models ship faster and how to keep that alignment from going stale
- leadership-fundamentals
- leadership-practices
7 min read
Law of Triviality
Why teams spend more time debating trivial details than important decisions, and how to allocate attention more effectively
- leadership-fundamentals
2 min read