3 ms·
I'm part of a company that went from a boring VCS strategy to jumping on the monorepo bandwagon against my advice to keep our git usage simple. It's been fairly
by vorpalhex 8y ago
I'm part of a company that went from a boring VCS strategy to jumping on the monorepo bandwagon against my advice to keep our git usage simple. It's been fairly terrible - merge conflicts, code going to the wrong environment, nobody can actually do a hot patch, and even long running feature branches which should be stupidly simple run into immense problem.
It also caused issues with our npm repo solution, and has created the worst case of dependency lock we've ever had.
Do yourself a favor and say no to monorepos. It is massive complexity for no benefit.