I always love that circular logic. "Hey our developers can't make modules correctly! Let's make the API boundaries using HTTP calls instead, then they'll sudde

I always love that circular logic. "Hey our developers can't make modules correctly! Let's make the API boundaries using HTTP calls instead, then they'll suddenly know what to do!" And that unsupervised junior? At one place I joined, that unsupervised junior just started passing data he "needed" via query string params in ginormous arrays from microservice to microservice. And it wasn't a quick fix because instead of using the lovely type system that TELLS you where the stupid method has been used, you've got to go hunting for http calls scattered over multiple projects. All you've done is make everything even more complicated, if you can't supervise your juniors, your code's going to go sideways whatever. Microservices don't solve that at all and it's pure circular logic to claim otherwise. If your team can't make good classes, they can't make good APIs either. And worse still, suddenly everything's locked in because changing APIs is much harder than changing classes.