DevOps Paradox · 2026-07-29 · 42 min
#361: Picture a 6,000-line pull request landing in your project from someone you've never heard of. Every test passes - yours, theirs, all of it. And you can tell it was generated. Not assisted. Generated. What do you do with it? Viktor's first move is to poke the premise: how do you even know it was generated and not assisted? You can't. Nobody can. That distinction is already gone. So the real question isn't whether AI wrote it. It's what a maintainer is for. Viktor's answer is blunt - a maintainer's first job is to guide people in and help them contribute, and if you think your job is mainly to write code, you picked the wrong role. The moment you allow PRs, you stopped being an individual contributor and became a manager. That's the job. You don't get to complain about the job you signed up for. Don't want it? Fine - do what Ghostty did, do what curl did, turn PRs off and say so out loud. Just don't hide behind unknown contributors, because every single person on your project was an unknown contributor on their first commit, including you.
DOP 362: Feature Flags vs Canary Deployments80 / 100
DOP 358: Just-in-Time Access for AI Agents71 / 100
DOP 356: Warehouse Robots Are a Distributed System83 / 100
DOP 355: Why AI Coding Slows Down Code Review67 / 100
DOP 354: Your Dead Founder Trains New Hires73 / 100