A Monorepo Can't Save You From Your Own Corporate Dysfunction
summary
Central claim: a monorepo does not fix organizational dysfunction; it merely exposes it. Examples include loony devs who bring incompatible code, the knight with high standards who piles on rules, the caped reviewer who bottlenecks merges, and Sneetch-like teams protecting status. Concrete tools and fixes: use NX tooling but accept multiple repos when needed, split NX core and closed-source work, delegate and train reviewers, realign incentives, and measure whether code sharing and review delegation actually speed delivery instead of just adding policy overhead.
AI-written summary · about
chapters (5)
- 0:00The monorepo myth
- 2:21Interpersonal challenges
- 4:08Archetypes in the workspace
- 9:15Managing developer types
- 13:55Practical team solutions
related talks
16mHow We Moved to a Monorepo
15mStories from the Trenches
21mScaling Internal Collaboration with Open Source Operating Models
45mEvery Software Org is Dysfunctional
52mUnderstanding UnHealthy Syndromes of Software Delivery
20mDoing Things the Hard Way
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
58mRefactoring the Architect’s role