Our company currently has our code base split across 30+ repos.

Historically, there was one single repo, but over time it was decided to split them up. Some are common helpers, some are vertical feature slices - front and back end. Our current process builds a nuget package where appropriate for shared helpers, classes, etc, and that's reused across other projects as needed. We also have micro-front ends in react and angular included in some of these projects.

We're having many problems though, the biggest being maintenance. We're spending roughly 25 hours a month just doing package updates - upgrading packages, deploying to dev, test, deploy to staging, test, repeat x 30 times.

Also mindful that in AI world, it's easier to have the whole code base in one so the tooling has a clearer view of the whole thing.

I've found lots of articles on how to migrate to a monorepo, but very few on people's experiences of doing it.

Has anyone gone through such a project? How did you find it? Was it worth it? Any pain points, or lessons - good or bad - to share?

Hi everyone.

Alongside being a developer for the past 15 years, I've been helping leaders in tech who look successful on the outside but are constantly on the edge of burnout due to others' expectations and being always on for the past 4 years as a coach.

I'm looking to have short conversations with leaders in tech like you to understand whether something like this is relevant to you. In return, I would share what I learned over the past 4 years that leads technical leaders burn out and what needs to change so it doesn't happen again.

Let me know if you'd be interested in having a chat.

P.S. No sales or promotions from my side - I want to help as many people as I can so I want to understand the problems leaders are facing nowadays.