Connect your Claude, Codex or OpenClaw for full transcripts on millions of podcasts. Two week free trial, cancel anytime.

Start free trial →
DN Dave Nunez Dave Nunez On MLOps.community

“Agents are going to do the same thing, but worse, because they're going to write something down, and you're going to trust it because you're going to think, well, it's here. I don't have to ask the person who actually owns it, because something is written down by Claude, so I'm going to trust it. It's more dangerous.”

MLOps.community · AI Builders · November 2026

“Agents are going to do the same thing, but worse, because they're going to write something down, and you're going to trust it because you're going to think, well, it's here. I don't have to ask the person who actually owns it, because something is written down by Claude, so I'm going to trust it. It's more dangerous.” — Dave Nunez, MLOps.community

Context

Nunez had just described a friend's weeks-long production incident caused by an agent acting on a stale document, and a similar one at Uber caused by humans not updating docs. His point is that AI-written docs get trusted too easily.

Transcript

MLOps.community Around 14:09 into the episode
Dave Nunez

…prototype and then that gets specced out. And then like that alone is so much more useful. So that's probably to answer your question, like I would say, look at the stuff that can just be distilled down to a diagram, a workflow, a checklist, and like get rid of all the old context. Just delete it.

Demetrios Brinkmann

…Notion docs or the Google Docs that give you English, but then you've got code that goes with it. And if the majority of the stuff doesn't match or it just is overwhelming to the agent, you're really rolling the dice on if you're going to get anything valuable back from the query that you've asked.

Dave Nunez

Yeah, absolutely. And code is pretty pristine. That's what the agents were trained on. So what they're optimized for. And if you have dead code, delete it, but agents are going to know like how to traverse that and what to get out of it. But yeah, you're right. They start to get confused when they're taking, okay, this is the code base, but your name is tied to this document conflicting with what's in the code. And it's conflicting in this old JIRA or linear task. So like, I'm just going to flip a coin because I'm meant to please you. And your name is on the code and your name is on the task. Your name's on the doc. So I'm just going to make a call here. And it's so great because I'm like a magnet for friends at companies where they're like, I just heard the other day, somebody was like, we had the worst incident I've ever experienced in my career. It was weeks of cleanup because an agent made the wrong call based on a document. Like it is, this happened to me at Uber, except it was humans not updating the documents. Like agents are going to do the same thing, but worse because they're going to write…

Demetrios Brinkmann

Dude, that just makes me think about the people or the ones who have to actually clean up the mess once it happens because this is almost like a latent problem until it's not. And then you get some kind of an incident and somebody can't figure out what the hell is happening because the…

Dave Nunez

Yeah.

Demetrios Brinkmann

And or the agent is trying to figure it out and it's making mistakes because of documentation. And so you almost don't realize how bad it is until something goes wrong.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from MLOps.community