> However the optimal architecture according to this measure is a function of the problem domain. I agree with this. But domains typically evolve incrementally

> However the optimal architecture according to this measure is a function of the problem domain. I agree with this. But domains typically evolve incrementally -- and using the skillsets I mention you can evolve your code accordingly. [1] There is then the question of these cross-cutting, earth-shattering domain changes you mention. I'm not convinced my argument doesn't have a play here but regardless if these kinds of major domain changes are happening frequently enough to matter in this discussion then I think there's a different business-level problem going on. It's hard to talk abstractly about this for so long--until of course someone gets to building out these ideas more formally. Getting into concrete cases would be more fruitful. --- [1] That you can without cost tradeoff is my argument. Today these skills are so rare so you don't find orgs/codebases that do this properly--and therefore we have this fallacy that because it's prevalent that it's somehow necessary. We don't realize it's really a skills problem.