Here's the problem: > It doesn’t affect ownership. After the away team finishes its changes, the service ownership remains with the host teams. The away team m

Here's the problem: > It doesn’t affect ownership. After the away team finishes its changes, the service ownership remains with the host teams. The away team model also reflects how Amazon weakly assigns code ownership to service teams. The article quotes Martin Fowler to back this up: > Weak code ownership: Developers are allowed to change modules owned by other people. Module owners are expected to take responsibility for the modules they own and keep an eye on changes made by other people. However, this quote seems taken out of context. It is about individual developers making changes. When you have an entire team doing this for (months?) at a time, can maintainers really keep up with the changes and support them in perpetuity in addition to their other responsibilities?