I relate so much with this article I've had a previous experience with a backend monolith repo, and these days I have to deal with a backend that has 20+ repos. It is hell. Duplicated code, duplicated logic, duplicated tests, duplicated settings, an hell to introduce newbies to the architecture, async calls to external basic APIs that could've been just simple method calls.

I think that the one major disadvantage of having a big monorepo, is that with those multiple entry points, you might end up with a bunch of unused dependencies. But even that is manageable I think: you can have different package dependencies definitions whilst using the same codebase.

I've always worked with small teams (max up to 5 or 6 developers) and that's another point in favor of monorepos. I understand that big companies might want to have different teams working on different repos, for organisation reasons.

They don't have to be micro - they can just be services.

Yes. While it looks like there is no silver bullet for this, this looks like the better approach

I have no children, but I find this an interesting topic, because I have small cousins and friends with children. I find it quite disturbing to see the kids online, with their eyes on screen all the time they are not sleeping. It is concerning and it doesn't look healthy, both for their bodies/minds but also for their future. Don't tell me children learn something useful in TikTok, albeit some creative ideas, but in long term, most of it is crap. I honestly look at these children, and can't quite fathom what their future will be. Hopefully they will pop out/unplug off their drug, but... yeah.

I changed mainly because my manager was an asshole