It does make quality assurance an absolute nightmare, I would know, our application is like this to the 10th degree. Config on top of config on top of setting on top of options.
But if you also want your product to be productive for a way array of use cases, it's necessary. You need to think about your market.
Which is why you should think about how these options interact and compose at the start, as opposed to only adding options in an ad-hoc manner (whether you do it willy-nilly or only when your arm is really twisted)
"You mean we shouldn't use 10 layers of abstraction and 274 libraries to achieve our goal ? I mean, we use a lot of resuources, but look how polished the UI is: everything is flat. "
Thank god the RAM prices have risen. Maybe some people will start to programm with their heads instead of their (AI) IDE.
But if you also want your product to be productive for a way array of use cases, it's necessary. You need to think about your market.