Comparison
Code ownershipvsData ownership
Code ownership
you opened a pull request against another team's repository and it sat there for eleven days.
Who is accountable for a piece of code: reviewing changes, running it, and being paged when it breaks. Strong ownership makes quality and on-call clear and makes cross-team change slow; collective ownership makes change fast and quality diffuse. Neither is right in general, and the failure to state which one is in force is what produces both the eleven-day review and the directory nobody maintains.
Full entry →Data ownership
the table is wrong and the question 'who owns this' takes two days and three Slack channels to answer.
A named team accountable for a dataset's correctness, freshness and lifecycle. Without it, quality problems are everyone's to notice and nobody's to fix, which is the default state of any warehouse over a certain size. Ownership recorded in the catalogue rather than in someone's memory is what makes an incident routable at three in the morning.
Full entry →