> A large fraction of demand for redundancy, introspection, abstraction and generalization comes from this. Sure, you need to invest into it but those are thin

> A large fraction of demand for redundancy, introspection, abstraction and generalization comes from this. Sure, you need to invest into it but those are things you can reuse for every app and feature you build. And those are not the reason why those systems are so complex, those are just ways to keep complex systems running and manageable. In most they also do not stand in the way of making system better but help in it. They need to exist because the architecture of system grew organically from smaller system over and over again and big restructurization was deemed not worth it. It's "just have a bunch more hardware and engineers" vs "we're not delivering features and we might not get rewrite right". And every time you throw money at the problem the problem becomes a bigger problem and potential benefits from "getting it right" are also getting bigger. But nobody wants to be herald that tells management "we 're going to spend 6-12 months" for somethinkg that have few years of pay-off