“We have been in a period of the last couple years where you're allowed to blame Claude. But as a few performance review cycles come around, people realize, oh, I own reliability, and my team's docs went down, or some other team's docs caused it that were written by Claude, but I own reliability. I'm getting dinged in performance reviews. All of a sudden, they're going to start to care.”

Yeah. And we have been in a period of the last couple years where you're allowed to blame Claude. You're allowed to blame the agents if something goes wrong. But as a few performance review cycles come around, people realize like, oh, I own reliability and my team's docs went down or some other team's docs caused it that were written by Claude, but I own reliability. I'm getting dinged in performance reviews. All of a sudden, they're going to start to care. Things aren't going to be as like as laissez-faire and YOLO as before of just like trading, you know, blindly trading what Claude says, blindly publishing it, because now you're responsible. So that's the when people ask me about docs, like what tool should we use? What should we do a style guide? I'm like, start with accountability because if you put a name to a doc set, just like a code base or a repo, people will figure it out how to care. And the next step of that is during performance reviews, like put it on the job ladder. Like, are you responsible for the documentation? People will figure it out. It will all cascade. Like, smart people will figure it out. And I think that's just kind of been blown up the last…