[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"term-c\u002Fcode-custody-battle":3,"related-c\u002Fcode-custody-battle":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Fc\u002Fcode-custody-battle.md","Code Custody Battle",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"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.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"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.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We're in a code custody battle over the auth module again, nobody wants to claim it.\" \u002F \"Define ownership before the next code custody battle breaks out.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"vibecoding","Two teams, one shared module, and neither wants to admit they both broke it in the same sprint.","beginner","md","c",{},true,"\u002Fterms\u002Fc\u002Fcode-custody-battle",[49,50,51,52,53],"Bus Factor","Blame","Knowledge Silo","Incident","Code Review",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fc\u002Fcode-custody-battle","xGJYAJgrUQIRAFOsDg073JunJdmR6Oj5tEjeYGJOUrs",[61,66,69,73,77],{"title":50,"path":62,"acronym":6,"category":63,"difficulty":64,"description":65},"\u002Fterms\u002Fb\u002Fblame","git","intermediate","Git blame shows you who wrote each line of a file and when.",{"title":49,"path":67,"acronym":6,"category":40,"difficulty":42,"description":68},"\u002Fterms\u002Fb\u002Fbus-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.",{"title":53,"path":70,"acronym":6,"category":71,"difficulty":42,"description":72},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":52,"path":74,"acronym":6,"category":75,"difficulty":42,"description":76},"\u002Fterms\u002Fi\u002Fincident","cicd","An incident is when something has gone wrong in production and users are affected.",{"title":51,"path":78,"acronym":6,"category":40,"difficulty":42,"description":79},"\u002Fterms\u002Fk\u002Fknowledge-silo","A knowledge silo is when critical information is trapped with one person or team and nobody else has access to it.",1792528071870]