Building Actionable Code Ownership
summary
Pinterest codifies ownership for API endpoints so each request maps to a responsible project, not an individual team, and applies that to over 1,700 endpoints across 70+ teams. Implementation uses an owned_by decorator that registers entities into a database, enforces owner validation on commit, integrates with Slack/PagerDuty (including an audit of pagerduty settings), and ships self-serve dashboards and runbooks. The contract is project-based ownership with versioned docs, POCs, and templates to make ownership actionable and reduce incident ambiguity.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:45Why is it important to think about ownership?
- 2:01Why is ownership difficult?
- 5:31How to define Ownership?
- 7:29Technical Solutions Ownership should be codified and queryable
- 10:20Making Ownership Actionable Empowering owners
- 12:28Communications
related talks
29mWho Owns What: Ownership Culture while Bitzscaling
21mTeam Ownership - Who Owns Production
27mLaying the Cultural and Technical Foundation for Big Rails
40mAutomated Governance in Practice
27mPillars of the Successful API Governance
22mA Dual Approach to Accountability Engineering
26mThe Wonders of Onboarding: The Ultimate API Management Adventure
32mCode First, Ask Questions Later