Ownership is important to be explicit about, less as a means of assigning blame, but more as a means of coordination and resource allocation. The author is usi

Ownership is important to be explicit about, less as a means of assigning blame, but more as a means of coordination and resource allocation. The author is using ownership as a tool to avoid responsibility, and is thus creating an `us vs them` mindset rather than an `us vs the problem` mindset. Having a strong definition of ownership (like committing your organizational structure to your monorepo as config file) is invaluable for building tooling. If you have a strong definition of code ownership it allows for things like people less familiar with a particular piece of code being able to make changes with the approval of the owners, while simultaneously notifying them of the change. Likewise, if you are working on a platform that multiple teams use, you can write tooling that automatically assigns bugs or tickets. Ownership problems and "us vs them" is a clear sign of poor leadership. Most devs that experience it become cyncial or hostile without being able to understand that it is leadership that failed them.