Hi! Thanks for your words.

I disagree on "the must avoid monorepos" part, this is because it will mainly depend on your organization's workflows. Just think that Google, Facebook and Microsoft work using monorepos, we may not like monorepos at all, but they can't be all wrong.
Most complicated tasks (not only in software development) that take us out of our confort zone are prone to be rejected first. Our organization embraced the cost and difficulties in adopting monorepos, and so far it has worked pretty well, but saying it works for us doesn't mean it will work for all companies. Monorepos are in no way the holy grail of development.