What is your spiciest take on monorepos
twitter.com
What is your spiciest take on monorepos
1–6 of 6 posts
Re: What is your spiciest take on monorepos
#2There is no such thing as a true monorepo company.
Re: What is your spiciest take on monorepos
#3Most programmers aren't mature enough, or smart enough, to handle a monorepo. It requires too much interaction with code owners, reviewers, and ongoing churn.
Re: What is your spiciest take on monorepos
#4I use monorepo approach all the time in my work, it works great for me, the disadvantages is when it comes working with others, a lot of my peers get confused working with it, it also isn’t the best for say granular access compared if you have everything in separate repos.
Re: What is your spiciest take on monorepos
#5Most programmers aren't mature enough, or smart enough, to handle a monorepo. It requires too much interaction with code owners, reviewers, and ongoing churn.
Interesting. Curious to know what you think of this
https://graphite.dev/blog/there-are-no-true-monorepo-compani...
Re: What is your spiciest take on monorepos
#6Most programmers aren't mature enough, or smart enough, to handle a monorepo. It requires too much interaction with code owners, reviewers, and ongoing churn.
Interesting. Curious to know what you think of this https://graphite.dev/blog/there-are-no-true-monorepo-compani...
Technically google isn't a monorepo, but when I worked there for 7 of the years I worked in google3, which was truly a monorepo, except for Android, and the kernel, and some open source projects... OK, not a monorepo.