> IME, most consternation comes from people adopting a mono repo without adopting a build/dependency graph tool (like Bazel, buck or pants). That seems like a

> IME, most consternation comes from people adopting a mono repo without adopting a build/dependency graph tool (like Bazel, buck or pants). That seems like a build problem, not a Git problem. > An additional source of strain is from people abusing the repo (checking in large binaries, third party dependencies, etc). That is not necessarily abuse. In fact, it is a good practice in many cases! > A third is when people try to do branch-based feature development, instead of the “correct” practice of only deploying master (or weekly cuts of master). I am not sure what you mean by branch-based development, but I don't see why that would be a specific problem of monorepos.