Beaver Duty

Beaver Duty

Logs of Duty: System Ownership

A comprehensive guide to avoiding responsibility at scale.

Matt's avatar
Matt
Dec 27, 2025
∙ Paid

Rule #1: Assume it is not you. If your changes break something, it’s not your problem, it’s the owner who didn’t review carefully enough.

Rule #2: Ask who the owner is in Slack. And enjoy watching three teams tag three other teams.

Rule #3: Check the Git history. The last commit was six months ago by someone who has already left the company. So is code re…

User's avatar

Continue reading this post for free, courtesy of Matt.

Or purchase a paid subscription.
© 2026 Matt · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture