OF Obie Fernandez On O11ycast

“Everyone is just using Claude Code or whatever their agent is to write those things now. And humans, as a general rule, don't like reading AI output. So at worst, they just won't read it, and at best, they might have their agent read it for them. But at that point, what's the point? If a human's not going to write it and a human's not going to consume it, then you're just generating a bunch of stuff.”

O11ycast · Hands-On Engineering Podcasts · November 2026

“Everyone is just using Claude Code or whatever their agent is to write those things now. And humans, as a general rule, don't like reading AI output. So at worst, they just won't read it, and at best, they might have their agent read it for them. But at that point, what's the point? If a human's not going to write it and a human's not going to consume it, then you're just generating a bunch of stuff.” — Obie Fernandez, O11ycast

Context

Obie explains why his company stopped keeping plans and requirements in wiki tools like Notion or Confluence. He prefers a constantly updated knowledge graph that agents turn into whatever view a person needs.

Transcript

O11ycast Around 26:20 into the episode
Obie Fernandez

…be said maybe for Google Docs or any place where people kind of like documented something and then it just stays there and is not constantly updated unless there's some sort of energy invested to fight entropy for those particular documents. But I think that whole class of information is dead.

Speaker 2

That like static, write it down, leave it there, expect it to hold still. That's like getting the results and checking the box. We can do better than that. This knowledge is always evolving. It's an event stream that gets distilled.

Obie Fernandez

Yeah. You know, I'm partial to the knowledge graph representation. That's why I put, you know, invest so much in it. But the whole confluence, notion, you know, pretty much anything where there's like kind of a preparation of requirements or plans or whatever, and then it gets put into a written form. One of the practical reasons is that everyone is just using clot code or whatever their agent is to write those things now. And humans, as a general rule, don't like reading AI output. So at worst, they just won't read it. You know, they might skim it. And at best, they might have their agent read it for them. But at that point, you're like, what's the point? You know, if a human's not going to write it and a human's not going to consume it, then you're just generating a bunch of stuff, which I call comp flop, which is.

Speaker 2

It's doing the same thing faster. That's not interesting.

Obie Fernandez

It really isn't interesting. You know, it's, it's one of those things where it's a horseless carriage kind of thing.

Speaker 2

Right. Whereas your agents can at any point build you a custom UI to understand what you need to understand based on the knowledge graph, which is a more abstract representation and constantly evolving based on the distillation of the events.

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

More from O11ycast