Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

DevOps Paradox

DevOps Paradox artwork

DOP 361: When Code Got Cheap, Reviewing Got Expensive

Jul 29, 202642 minAudio

#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. A software developer says send me anything but a PR and lists four reasons: unknown contributors are a security risk, supply chain attacks are real, style disagreements eat maintainer time across time zones, and LLMs killed code-writing as the bottleneck so the stranger's PR doesn't help with the parts that are still hard. Viktor grants the security point and then points at XZ - social engineering, a long con, zero AI required. The risk was always there. What changed is quantity, not the percentage. And the maintainer who thinks a manual, line-by-line review still works in 2026 is, in his words, terribly wrong. Viktor guesses he can review 6,000 lines in about the time it takes to hand-review 600. CodeRabbit and Greptile clear the obvious junk so he can spend his attention on architecture and the feature itself - the stuff he never had energy for after slogging through nitpicks by hand. His read on the whole backlash: there's a new third group of maintainers now, the ones who aren't good enough with agents to fight agents, and they're the ones falling behind. Writing code is cheap. Reviewing it well is the expensive part - and the ones who refuse to use agents to review are drowning while blaming the contributors. There's a cost angle too. If you don't have tokens, you're in trouble, and not everyone can afford them. Tokens are becoming table stakes, like an internet connection. Which raises the question: what happens to open source when the reviewing tools cost money the maintainer doesn't have? I don't want your PRs anymore https://dpc.pw/posts/i-dont-want-your-prs-anymore/ YouTube channel: https://youtube.com/devopsparadox Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/ Slack: https://www.devopsparadox.com/slack/ Connect with us at: https://www.devopsparadox.com/contact/

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. DOP 377: KubeCon North America 2026 Review

    Nov 18, 202637 minAudio

    #377: Every software company that ever thought about sponsoring KubeCon already sponsors KubeCon. So where does it grow from here? Ask what on the expo floor wasn't AI, and you get two answers: the coffee and the puppy...

    Credit the people on this episode

  2. DOP 376: Secrets Management for AI Agents

    Nov 11, 202641 minAudio

    #376: How many secrets can your coding agent reach right now? You gave it a token so it could get work done. It might have passed that token to every agent it spun up. Somewhere along the way, you stopped reading the...

    Credit the people on this episode

  3. DOP 375: AI Writes the Code. Who Understands It?

    Nov 4, 202649 minAudio

    #375: An agent can crank out 200 or 300 lines of code a minute. You can maybe review 40. So who's actually supposed to understand what just got merged? Maybe nobody ever did. Did you really read every line of every PR...

    Credit the people on this episode

  4. DOP 374: Does AI Make Companies More Productive?

    Oct 28, 202656 minAudio

    #374: Your company is paying for the AI licenses, and now there's a number attached. Two to three times the output, every day, or else. Can you hit it? If they're counting lines of code, sure. But you aren't the...

    Credit the people on this episode

  5. DOP 373: Are Layoffs Really Because of AI?

    Oct 21, 202645 minAudio

    #373: A company lays off 4,000 people the same day it posts record revenue, and the stock jumps. Is that really because of AI? Or just a really good press release? Layoffs used to mean a company was bleeding cash. Now...

    Credit the people on this episode