Monorepos are most painful when all the components are heavily coupled. Maybe a bunch of unrelated stuff in a single compilation unit (e.g. package) results in

Monorepos are most painful when all the components are heavily coupled. Maybe a bunch of unrelated stuff in a single compilation unit (e.g. package) results in a lot of waste. And then people just end up not having clear interfaces and boundaries and ownership. But I guess that's not a result of a monorepo inherently. It's just the result of poor engineering leadership.