Code Custody Battle
ELI5 - The Vibe Check
Two teams, one shared module, and neither wants to admit they both broke it in the same sprint. Code custody battle is the tense, passive-aggressive standoff over who actually owns a file, usually surfacing right after something in it breaks and everyone needs to agree, quickly, that it was somebody else's responsibility.
Real Talk
A code custody battle occurs when ambiguous or shared ownership of a module, service, or file leads to disputes over who is responsible for maintaining, reviewing, or fixing it, especially after an incident. It's a symptom of unclear ownership boundaries and is typically resolved by explicit ownership assignment, like CODEOWNERS files or defined team boundaries, rather than by relitigating blame after each incident.
When You'll Hear This
"We're in a code custody battle over the auth module again, nobody wants to claim it." / "Define ownership before the next code custody battle breaks out."
Related Terms
Blame
Git blame shows you who wrote each line of a file and when.
Bus Factor
Bus factor = 1 means one person leaving (or getting hit by a bus) destroys the project. They're the only one who knows how the payment system works.
Code Review
A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.
Incident
An incident is when something has gone wrong in production and users are affected.
Knowledge Silo
A knowledge silo is when critical information is trapped with one person or team and nobody else has access to it.