One of the reasons we did this work is because we saw this happening to people who were perceived as really high performers. In the study, 14 percent of workers said they had experienced mental fatigue that results from excessive use of, interaction with, and/or oversight of AI tools beyond one's cognitive capacity.
"We used to call it an engineer, now it is like a reviewer," Khare told Business Insider. "Every time it feels like you are a judge at an assembly line and that assembly line is never-ending, you just keep stamping those PRs." Khare wrote a lengthy essay titled "AI fatigue is real and nobody talks about it." In it, he wrote that AI fatigue is "the kind of exhaustion that no amount of tooling or workflow optimization could fix."
But many engineering teams are noticing a trend: even as individual developers produce code faster, overall project delivery timelines are not shortening. This isn't just a feeling. A recent METR study found that AI coding assistants decreased experienced software developers' productivity by 19%. "After completing the study, developers estimate that allowing AI reduced completion time by 20%," the report noted. "Surprisingly, we find that allowing AI actually increases completion time by 19%-AI tooling slowed developers down."
When Peter Drucker first met IBM CEO Thomas J. Watson in the 1930s, the legendary management thinker and journalist was somewhat baffled. "He began talking about something called data processing," Drucker recalled, "and it made absolutely no sense to me. I took it back and told my editor, and he said that Watson was a nut, and threw the interview away."
