Monorepo: please do
Observe how the verb &quot;force&quot; gets used 6 times. Monorepos &quot;force the conversation.&quot; You the individual contributor are &quot;forced to deal with the situation&quot; and &quot;forced to see the upfront cost&quot; of breaking contracts. Your team is forced to &quot;look up from their component, and see the perspectives of other teams and consumers.&quot;<p>All this forcing people to do things the Right Way (<i>my way</i>) is surely part of the pushback against monorepos.<p>But set that aside for the moment. Let&#x27;s suppose defaults <i>should</i> force people to do things the Right Way, and that we also know what the Right Way is.<p>Instead of letting anyone sloppily depend on any code checked into the monorepo, shouldn&#x27;t we <i>force</i> people to think long and hard about contracts between components -- the default concern in a polyrepo architecture? When and how to make contracts, when and how to break contracts? Isn&#x27;t this how Amazon moved past their monorepo woes, adopted SOA, built AWS, and became one of the largest companies on earth? Heck, isn&#x27;t this how the Internet itself was built?