I think the goal of any such pursuit is to reduce/manage the cognitive load that any one person has to deal with while they are trying accomplish something. Th

I think the goal of any such pursuit is to reduce/manage the cognitive load that any one person has to deal with while they are trying accomplish something. Things like "Separating control structure from problem domain" enable separation of concerns so that the person deal with resource utilization – efficiency/capacity-planning and scalability can be an expert in systems domain and doesn't have to deal with functional domain understanding and its complexity (and vice versa). Solving for separation of concerns in such a way that it also enables separation of roles and responsibilities and hence facilitates developing expertise/specialization in a particular orthogonal discipline is super powerful. In my experience, this is one of the most effective ways to scale a fundamentally human endeavor of building large software projects.