Code ownership is a culture problem, not a technical one
Code ownership is a culture problem, not a technical one When a group of teams with roughly twenty engineers writes and supports a codebase, but only two engineers can approve changes to its core parts, it can look like a sensible technical constraint. Someone needs to protect quality. Someone needs to make sure new features do not break production. Someone needs to preserve the history and context of the system. All of that is true. But over time, having only a few engineers act as code owners can reduce quality instead of protecting it. Not because those engineers are doing a bad job, but because the ownership model changes how everyone else behaves. ...