Monorepo: please do! – Adam Jacob – Medium

You should choose a monorepo because the default behavior it encourages in your teams is visibility and shared responsibility, especially…

Click to view the original at

Hasnain says:

This was a refreshing take on monorepos. Most arguments for/against them keep on the technical side, talking about how the repo gets large and slow (bad!) or the benefits of being able to make codebase wide changes in an atomic setting (good!), and debate the usefulness/commonality of each.

This instead focuses on the organizational cost, and how monorepos force you to make certain decisions/costs explicit, like the cost of maintaining separate branches/forks of internal code, and of having to coordinate releases of older code.

This is critical for larger organizations where it's very easy to sweep these costs under a rug unless there is a forcing function.

Worth a read.

Posted on 2019-01-04T05:25:44+0000