I think this is a great point, and shouldn't be just hand-waved away like you hit some bizarre edge case of Monoliths. Monoliths can have crippling downsides -

I think this is a great point, and shouldn't be just hand-waved away like you hit some bizarre edge case of Monoliths. Monoliths can have crippling downsides -- just different flavours of downsides from Microservices. What you gain in network latency and DRYness, you can lose in Autonomy and Breadth of codebase. Microservices vs Monoliths - just like everything else - is a question of tradeoffs, and making informed choices about when to apply them, and how to mitigate their downsides. The slightly more nuanced point in the OP's article is that adopting any engineering practice and blindly following as though your identity is linked to it, is a bad move.