>Everyone's favorite law to cite but I rarely see a lot of examples If you're looking for experimental validation of Conway's Law, the best work I'm aware of w

>Everyone's favorite law to cite but I rarely see a lot of examples If you're looking for experimental validation of Conway's Law, the best work I'm aware of was done by Microsoft Research analyzing the Windows Vista development effort[0]. They found that organizational measures (eg. how high up in the org structure do you have to go to find every developer who contributed code to a particular DLL, etc.) were significantly better predictors of post-release code quality than traditional metrics like churn, complexity, coverage, dependencies, or pre-release bug counts. If your company builds software, there's a tax to pay if the code architecture and human architecture are poorly aligned. The bigger that misalignment, the bigger the tax. Conway's Law misalignment is like technical debt in the sense that it's always there at some level, and there are times when it's important to reduce the cost and there are times when it's better to accept the cost and focus on other taxes/debts. [0]https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/tr-2008-11.pdf https://www.microsoft.com/en-us/research/wp-content/uploads/...