By large scale do you mean large software or large amounts of developers? Because there's some absolutely massive software in terms of feature set, usefulness and even LoC (not that that is a useful measurement) etc out there made by very small teams.
I'm not sure that you've got the causal relationship the right way around here re: architecture:team size.
Sure I agree with that, but microservices are just one of many ways to modularize software/achieve separation of concerns.
I assumed you were talking about team size specifically because that is the thing that a microservice architecture uniquely enables in my experience.
I think you might be missing that Swizec edited the quote, crossing out microservices and correcting it to modular systems. It seems to me you're both in violent agreement.
What does team size have to do with this? Small teams can (and should) absolutely build modularized software ...
You simply cannot build a [working/maintainable] large piece of software if everything is connected to everything and any one change may cause issues in conceptually unrelated pieces of code. As soon as your codebase is bigger than what you can fully memorize, you need modules, separation of concerns, etc.