<story><title>Linux follows an inverse form of Conway&apos;s Law</title><url>https://medium.com/@aserg.ufmg/does-conways-law-apply-to-linux-6acf23c1ef15</url></story><parent_chain></parent_chain><comment><author>tytso</author><text>Conway&amp;#x27;s Law absolutely applies to Linux.  The trick is to remember that the communication patterns that Linux is optimized to reflect is &amp;quot;git tree pulls&amp;quot;.   Over time, things have been factored to minimize the amount of cross-tree merge conflicts.  That way we can decentralize the development effort, and worry much less about conflicts when Linus has to pull from a hundred-odd git trees (many of which have sub-trees that were merged together by the subsystem maintainers before Linus then pulled them into his tree).   But &lt;i&gt;that&lt;/i&gt; is the primary communication pattern which is critical, and we have absolutely optimized how the code has been laid out to minimize communication difficulties --- when defined in terms of merge conflicts.</text></comment>
<story><title>Linux follows an inverse form of Conway&apos;s Law</title><url>https://medium.com/@aserg.ufmg/does-conways-law-apply-to-linux-6acf23c1ef15</url></story><parent_chain></parent_chain><comment><author>smitherfield</author><text>Misleading y-axis strikes again: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;cdn-images-1.medium.com&amp;#x2F;max&amp;#x2F;800&amp;#x2F;1*MiF0VmKW19IC3OlVDISgZA.png&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;cdn-images-1.medium.com&amp;#x2F;max&amp;#x2F;800&amp;#x2F;1*MiF0VmKW19IC3OlVDI...&lt;/a&gt;</text></comment>