That’s a way to reduce the output of your developers - keep them feeling busy but don’t get features to customers any faster. If someone proposed some new dogm

That’s a way to reduce the output of your developers - keep them feeling busy but don’t get features to customers any faster. If someone proposed some new dogma to live by: 1. Don’t use method parameters - write some IDL instead, add some steps to your build process to auto gen some bindings from the IDL. Introducing a dependency (with its own security patch lifecycle) in the process. 2. Don’t call a method in a library - instead setup mutual authentication and transport layer security, open a port (probably add load balancing and failover routing), set a reminder to maintain ssl certs before they expire, add distributed logging collectors, add endpoint instrumentation, add service cataloguing and lookup, slow each call down by serialising then deserialising the request then repeat that serdes overhead for the response. … You’d rightly point out their suggestions add complexity and slow things down, what was so bad about calling a library method in the process’s address space in the first place.