Interesting research in HBR today about how the productivity boost you can get from AI tools can lead to burnout or general mental exhaustion, something I've noticed in my own work https://simonwillison.net/2026/Feb/9/ai-intensifies-work/
AI Doesn’t Reduce Work—It Intensifies It

Aruna Ranganathan and Xingqi Maggie Ye from Berkeley Haas School of Business report initial findings in the HBR from their April to December 2025 study of 200 employees at a …

Simon Willison’s Weblog
AI Doesn’t Reduce Work—It Intensifies It

One of the promises of AI is that it can reduce workloads so employees can focus more on higher-value and more engaging tasks. But according to new research, AI tools don’t reduce work, they consistently intensify it: In the study, employees worked at a faster pace, took on a broader scope of tasks, and extended work into more hours of the day, often without being asked to do so. That may sound like a win, but it’s not quite so simple. These changes can be unsustainable, leading to workload creep, cognitive fatigue, burnout, and weakened decision-making. The productivity surge enjoyed at the beginning can give way to lower quality work, turnover, and other problems. To correct for this, companies need to adopt an “AI practice,” or a set of norms and standards around AI use that can include intentional pauses, sequencing work, and adding more human grounding.

Harvard Business Review

@simon A way I've been thinking about this is that it intensifies work by intensifying technical debt.

I know there's been a huge backlash against that term, but when everyone is signing off on and shipping 1.5K lines of code at a go several times a week, common sense dictates that you're robbing Peter to pay Paul later.

@feoh

@simon

Yeah, I have been wondering about that. Is everyone really just pushing reams of code these days without talking, review, thinking, etc slowing it down? Who is signing off on this stuff?

@faassen (Leaving Simon out of this I'm sure he gets his ear bent plenty :)

Well that's the thing, right?

Is code review happening? Yes. Either your org does it or not.

Is code review happening at the level it used to before generative AI started pushing gigantor change sets into the development pipeline? That's what's unclear to me.

@feoh

Ignoring AI for a moment:

I know I can do high quality work on my own, in the right context, without review.

I have a lot of thoughts about PR code reviews; I know they slow me down a lot. They run contrary to heavy repeated refactoring to mold things in the right shape. I also tend to prefer earlier points of collaboration, during pairing and such.

But in a team you aren't by yourself and you need to take others along even if that means slowing down one way or another. The goal of shared understanding is far more important than review

And I don't understand why AI would let you give up shared understanding.

@feoh @simon I feel like it might not be that. When I feel like AI has intensified my workload it isn't because I'm stuck cleaning up a bunch of tech debt, it's because I have a lot more leverage. The AIs work really fast and can do a lot of work so it's easy to get into situations where the process is blocked on you. Reviewing the work, scoping out the next work, etc.