Could you explain how you get around the knowledge silo problem? Fungibility across the team is useful for resource allocation and can prevent bottlenecks - for example if a part of the codebase is higher priority or someone is ill or on holiday.
Loose partitioning seems like it would work if either:
1. the partitions were similar/simple enough for other members to grok easily
2. the documentation and code sharing were thorough and extensive
I don't know how feasible it is to rely on (1) and (2) seems like it would cost an investment in time that would subtract from the efficiency gains of partioning. If it is (2) what are the exact reqs/mechanics for docs/PRs that seem to have worked?
I'm especially curious as "how to structure development teams" is something I am beginning to actively learn about.
Loose partitioning seems like it would work if either:
1. the partitions were similar/simple enough for other members to grok easily 2. the documentation and code sharing were thorough and extensive
I don't know how feasible it is to rely on (1) and (2) seems like it would cost an investment in time that would subtract from the efficiency gains of partioning. If it is (2) what are the exact reqs/mechanics for docs/PRs that seem to have worked?
I'm especially curious as "how to structure development teams" is something I am beginning to actively learn about.