4 ms·
At my current workplace, most top-level subdirectories in the source tree have a primary author. That person is (nominally) "owner" of that code. If they aren
by AnimalMuppet 8y ago
At my current workplace, most top-level subdirectories in the source tree have a primary author. That person is (nominally) "owner" of that code. If they aren't the one making changes, they're almost always at least the one doing the code review.
Bugs by default get routed to the person who wrote the code (presuming that we can tell which code the bug is in). If that person finds out the bug is somewhere else, the bug gets transferred to a new owner.
- catchmeifyoucan 8y agoThanks for sharing. What if that person leaves the company? Can that information get old.
- AnimalMuppet 8y agoPeople don't leave here very often. But, yeah, that would be a problem. Having someone else code review everything helps spread the knowledge, at least somewhat. But we definitely need to work on our bus factor...
- codingdave 8y ago> Bugs by default get routed to the person who wrote the code... That was the root of some very toxic teams I've seen. Because it built a lack of shared ownership as a team, it inspired competition instead of cooperation, and people would just ignore problems because "it wasn't my code". Admittedly, that is a problem with the leadership that took the team to that place, but I'd be interested in hearing counter-examples of how to avoid such pitfalls.
- deleted 8y ago[deleted]
- scarface74 8y agoI hate that attitude. Especially if a bug is impacting something I am doing, I’ll just fix it myself and let them know.