I switched teams from one with a communal codebase to one with code ownership (within the same org). The code ownership style has far better developer producti

I switched teams from one with a communal codebase to one with code ownership (within the same org). The code ownership style has far better developer productivity. But I think the issue is just not about team organization, but also of software architecture. I think with code ownership the modules need to be small enough so that if the owner exits unexpectedly from the organization someone else can pick up from where the previous owner left. With communal software that gets built and tested after each build its very easy to let the architecture slide into a structureless mud ball that works but nobody is quite sure how, especially with changes being diffused throughout the system with concurrent edits by different developers.l