i feel like we keep running into these problems repeatedly with a lot of our “disruptive” tech. scaling problems that come with usage in the real world. they’

i feel like we keep running into these problems repeatedly with a lot of our “disruptive” tech. scaling problems that come with usage in the real world. they’re “disruptive” until it gets to actual scale of the thing it was disrupting and reality smacks it around. many of our complex systems are bloated because the problems consist of a lot of tiny problems that require a complex and often messy bloat to solve. i already see this “let’s just rebuild it” attitude about some large software projects that are fairly modern. and repeatedly the people imagining a rebuild will fix the problem have little idea of complex systems and fractal depths of problems these systems must address as they scale in every possible direction. the people imagine a rebuild will somehow not require bug fixes, security patches, thousands of new layers of features, etc… etc… all done by dozens or hundreds of different people, each with different mental mappings of the overall system. i’m obviously not suggesting that we don’t build or attempt to streamline, but omg the number of times i’ve seen people completely… just utterly fail to understand why something in the real world may be bloated or messy is unreal. sure, it’s easy to be streamlined and agile as long as the product is new and not used in any kind of scale… until the product is used in reality, and it begins to scale, and the insane number of (very real) real world variety of complications smack it (and it’s cultists) into reality. sometimes things are bloated, not because the previous generations were stupid — they weren’t, we’re standing on the shoulders of giants — but because scaling will naturally come with impossible-to-prediagnose fractal depths of difficulties.