Although I strongly agree with it in principle, I'm growing seriously tired of the "simpler is better" argument. It hides all the nuance, hard work and, guess

Although I strongly agree with it in principle, I'm growing seriously tired of the "simpler is better" argument. It hides all the nuance, hard work and, guess what, complexity, that goes into making something simple. Simplicity is different to each person. What seems like unnecessary abstractions with complex inner workings often exist to actually hide other complexity away. Know the in and outs of Kubernetes? Maybe it's easier (simpler) for you than directly provisioning different pieces of infra. Have a team of over 10 [1] working on the same monolithic codebase? Productivity while maintaining sane separation of concerns might increase going for a more domain-service-oriented architecture [2]. How can we teach what simplicity is instead of just calling it better or saying arrogant platitudes like KISS? [1] yes, the number is that low, and often lower [2] yes, "micro" services does seem like a mistake in most cases