Post

Some gems: "Any operation over your repository that needs to be fast must be O(change) and not O(repo)." "Why do you want a monorepo?... You WILL NOT end up with an experience as tight as google31 or fbsource2. You WILL inherit a new set of problems that many-repo setup did not have."

The post is not anti-monorepo, not by any means. but it is truthful about what you are signing up for. And I love the framework to think about this problem, which is you should optimize for fast changes and iteration loops for developers.

0 reposts1 like

No replies yet.