The mental load of taking responsibility for code you didn’t write
There's a conversation happening right now about AI fatigue, and most of it misses the point.
On one side, you have the vibe coders. Ship fast, don't read it, trust the agent, move on.
On the other side, you have the skeptics. Reviewing code takes as long as writing it, so why bother. They won't ship code they don't fully understand, so they don't use the tools.
I'm in neither camp. And I think most working developers who actually care about their craft are in neither camp.
We read the code. We take responsibility for it. We use these tools at a high quality level. And that's exactly where the problem is.
The amount of code I can move through in a day now is astonishing. Things I never thought I'd be able to do. Scope I never thought I could hold. But to actually take responsibility for running that code, I have to work with the AI to understand the scope, then the code itself. Not skim it. Understand it. Because my name is on the commit.
The mental load this creates is unprecedented. Not because the tools are bad. Not because we're using them irresponsibly. Because we're using them well.
The cost of doing it right is what nobody is pricing in.
The ceiling we miss
There's a number that keeps surfacing from different angles. The BCG study in HBR puts it around three tools in parallel before productivity drops. Other voices in the industry land on three productive hours a day before burnout sets in. The research keeps pointing the same direction.
It's the same ceiling, measured differently. Somewhere around three to four hours of high-quality AI-assisted work per day, and the brain stops recovering overnight. Past that, you don't get tired from today. You get tired from the residue of three weeks ago.
Two long sessions a day, the kind I've been doing, is already past that. Doing the work well is the expensive part. Vibe coders can go all day because they're not actually holding the model. The rest of us pay for every hour past the ceiling, and the bill arrives later.
What actually releases the load
Short breaks don't work. I tried. The load doesn't release through rest, it releases through different kinds of engagement.
This took me a while to understand. When the work is supervisory — reading, judging, deciding, holding context — more of the same kind of input doesn't help. Sitting on the couch is still your brain in the same posture, just without the screen.
What releases it is engagement that uses something else. Physical. Social. Creative. Anything off-keyboard that isn't another version of the work.
And it can't depend on one source. If the only thing that releases your load is one person, one hobby, one ritual, you're one bad week away from having nowhere for any of it to go. Plural is the point.
The work doesn't end when you stop working. It ends when something else takes up the space.