And even if via LLMs we have convenient access to all the code... and tests and ADRS and product design and strategy documents and whatever else is written down...
we have assistance (we hold in more or less suspension of (dis)belief), but we still have
Organization models & roles, etc, are attempts at addressing this need for understanding, expertise, action (both local, and integrative/co-ordinating action) to have “organizational homes”… Recognizing that “broad scoped” (across) integration roles (management and more broadly scoped design & operations roles) need to inform and be informed by roles with more focused scope… The emphasis lands differently, but the underlying concerns are about how we organize to do system evolve-and-repair work
Thinking of Kent Beck’s “paint drip people” image, but in relation to systems. Our finite time, focus, attention, encounters, mean that our understanding of the system has this “paint drip” aspect to it — sometimes (and especially for more broadly scoped roles) broad brush across and sometimes deep drips into, but never deep drips throughout the whole system (and its various contexts)…