This is very accurate - microservices can be great as a forcing function to revisit your architectural boundaries, but if all you do is add a network hop and multiple components to update when you tweak a data model, all you'll get is headcount sprawl and deadlock to the moon.

I'm a huge fan of migrating to microservices as a secondary outcome of revisiting your component boundaries, but just moving to separate repos & artifacts so we can all deploy independently is a recipe for pain.

I know microservices and monoliths are a heated topic. However breaking up complicated code to preserve user experience is sometimes essential. However you can have machines that contain many services and that interact with each for performance if needed. You would put them into pod groups while deploying to kubernetes and have them call their service inside of the pod. This can increase performance and through put.