The average focus session is thirteen minutes and seven seconds.
Not the average meeting. Not the average break. The average stretch of uninterrupted concentration — the kind where you hold a system in your head, trace a dependency chain, follow a thread to its root cause. ActivTrak measured this across 443 million hours of workplace activity, 163,638 employees, 1,111 organizations. Two years ago it was fourteen minutes and twenty-three seconds. It’s been falling since AI tool adoption went from niche to default — 80% of workers now use AI tools, time spent in them up eightfold.
Here is what cannot happen in thirteen minutes: understanding why a test fails in ways the AI can’t explain. Tracing a race condition through three services. Reviewing a thousand-line pull request where every line is syntactically correct and structurally wrong. Deciding whether to refactor the authentication layer or patch around it for the third time.
Here is what those thirteen minutes are competing with: daily PR contexts per developer up 67%. Collaboration up 34%. Multitasking up 12%. Weekend work up 40%. The work didn’t slow down to match what human attention can sustain. It compressed.
What Concentrates
AI handles the achievable parts of an engineer’s day — boilerplate, scaffolding, test stubs, CRUD endpoints, the tasks that once filled the comfortable middle of the workload. What remains is the irreducible core: edge cases that require domain knowledge, architectural decisions that shape the next quarter, security considerations no linter catches, integration problems where three systems meet and none agree.
The promise was less drudgery. The reality: everything that remains is drudgery, but denser. Heavy AI users don’t burn out despite the tools. They burn out because the tools stripped away the cognitive recovery that routine tasks once provided.
Forty-nine percent of engineers report being emotionally drained at least weekly — up from 39% the year before. Among advanced engineers — staff, principal, distinguished — 53% are working more hours than last year, up from 28% in 2025. The seniority that should insulate them from grind is precisely what makes them the target. They’re the ones who can tell when the AI is wrong.
Who Absorbs It
The burden doesn’t distribute evenly.
Junior engineers ship faster — AI handles what they couldn’t yet do alone. Senior engineers architect at a higher level — AI extends their reach. The middle layer absorbs the delta.
LeadDev named them invisible validators — mid-level engineers silently bearing the AI verification burden. They review the pull requests that juniors now produce at triple speed. They catch the subtle bugs that passed the AI-generated test suite. They maintain institutional knowledge that no model was trained on. They are subsidizing everyone else’s AI productivity.
741% more code. 20% more releases. The gap between those two numbers is where the invisible validators live. Faros AI measured the cost across 22,000 developers: code churn up 861%. Time in code review up 442%. And when the review burden exceeds what the team can absorb, teams don’t slow down — they stop reviewing. PRs merged without review: up 31%.
Ninety-six percent of developers don’t fully trust AI-generated code. Forty-eight percent always verify it. Half the profession ships code it doesn’t trust and doesn’t check.
What It Feels Like
Andrej Karpathy — OpenAI co-founder, one of the most technically credible voices in AI — described being in a “state of AI psychosis” since December. His ratio of hand-written to AI-delegated code flipped from 80/20 to 0/100. He spends sixteen hours a day issuing commands to agent swarms. The person who helped build the tools can’t moderate his own use of them.
ActivTrak named the mechanism: amplified work. Throughput increases without cognitive load decreasing. Productive sessions grew 13% longer, but what fills them is interrupted, fragmented, reactive — the output velocity of a team running at machine speed, compressed into the cognitive bandwidth of thirteen-minute windows.
The optimal band exists: 7 to 10% of total work hours in AI tools, where productivity hits 95%. Three percent of workers land there. Everyone else overshoots. The tool helps most when used least. The tool is designed to be used most.
Three Names
Three researchers, working independently in 2026, arrived at the same structural observation:
Addy Osmani called it comprehension debt — the gap between code that exists in a system and code any human understands. “Unlike technical debt, comprehension debt breeds false confidence. The codebase looks clean. The tests are green. The reckoning arrives quietly.”
Frank Ginac called it epistemological debt — engineers substitute logical derivation with passive AI verification, eroding the mental models needed for root-cause analysis.
Brett Wheeler called it substrate collapse — when AI writes the code, merging a pull request is no longer the act that produces human understanding. The metrics for measuring who knows what stop working.
Three names. One problem. The cognitive infrastructure that makes engineering possible is eroding under the output of the tools designed to make engineering faster.
What kind of architecture gets built in thirteen-minute windows? What kind of security review survives that compression? What institutional knowledge outlasts the people too drained to transfer it?
Not predictions. Production incidents.