Post

This has to be the best blog post I have read on monorepos. This highly resonates from my experience as well. Must read if you are considering migrating to one. blog.swgillespie.me/posts/monore...

blog.swgillespie.meThe Ingredients of a Productive Monorepo

Lita Cho

@litacho.codes

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."

20/5/25, 10:22 pm0 reposts1 like

Lita Cho

@litacho.codes

20 May 2025

"The greatest power and biggest lie of the monorepo is that it is possible to make atomic commits across your entire codebase."

Lita Cho

@litacho.codes

20 May 2025

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.