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
Post 1 of 7
Conway's Law
Understanding the fundamental principle that software systems mirror the communication structure of the organizations that build them
Post 2 of 7
Architecture Is A Team Decision
Why software architecture decisions impact the entire team and how different architectural patterns affect development efficiency
Post 3 of 7
Microservice Architecture
Why microservices solve team coordination problems, not technical problems, and why most organizations would be better served by monoliths
Post 4 of 7
Brooks' Law
Understanding the counterintuitive principle that adding more developers to a delayed software project often increases the delay
Post 5 of 7
Lauffer's Law
How commercial framing shapes software architecture: software systems reflect the commercial narrative that justified their creation
Post 6 of 7
Law of Diffusion
How innovations spread through organizations and why technical excellence alone doesn't guarantee adoption
Post 7 of 7
Ubiquitous Language
How establishing a shared vocabulary between business and development teams eliminates translation overhead and improves software quality