3 ms·
I think in this case it's probably true for run of the mill bugs, but not for architecture and system design. But I just want to object to "we don't have any g
by IshKebab 3y ago
I think in this case it's probably true for run of the mill bugs, but not for architecture and system design.
But I just want to object to "we don't have any good evidence". This is the sort of thing that it's really hard to get scientific evidence for, but that doesn't mean we can't learn about it.
- di4na 3y agoI mean the problem is that we have quite good evidence of how to handle architecture and system designs problems. And it is not by finding them earlier. But by reducing their costs through looser coupling and incremental work. That is where all kind of agile and DevOps research showed.
- IshKebab 3y ago> we have quite good evidence of how to handle architecture and system designs problems We do? I seriously doubt that. New good and bad architectures are popping up all the time. And there are plenty of architectures that people totally disagree about, e.g. microservices. > But by reducing their costs through looser coupling In my experience loose coupling is something to be generally avoided where possible. It leads to spaghetti systems and unknown data flows. Pretty much the dynamic typing of architecture design. I'm not exactly sure what point you're trying to make though so I may have misunderstood...