Always Go With a Monorepo

Veteran CTO who built successful companies through empathic leadership and mastery of software delivery - from sustainable code to stakeholder trust. Now exploring the future of empathic and sustainable tech.

A good piece on why you don't need tons of repositories, but you need clear boundaries within your code.

Comments
  • @mbajur

    Can't agree more. I went down the multi repo path couple of times during my career and oh boy, never again. Now i'm pushing the alternative even further - [monolith](https://www.monolithic.dev/) all the way!

    / 0 replies
    linkreply