{
  "id": 6555023,
  "title": "AI scaled my work. But not my brain.",
  "url": "https://urgent.news/2026/09/10/ai-scaled-my-work-but-not-my-brain",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-10T07:19:41.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nikita_mkrv/ai-scaled-my-work-but-not-my-brain-6hd"
  },
  "original_language": "en",
  "account": "For the past year, the author has observed a significant change in their work habits when incorporating AI into their routines. While they accomplish more tasks in less time, they also experience a heightened sense of mental exhaustion. The difference is not just fatigue from a longer workday, but a deep mental drain, especially at the end of the week. This change is not due to the AI taking longer to perform tasks; instead, it's because the AI-driven processes are more intense than before.\n\nTraditionally, a developer's workday consisted of writing code, reading documentation, waiting for builds, encountering problems, and taking breaks. This structure spread mental effort throughout the day. With AI, the mental load becomes concentrated, creating a factory of continuous mental work. The AI agents work in parallel, each taking on different tasks—coding, refactoring, testing, and researching. The result is a rapid turnaround where one task's completion leads to the initiation of another. The human brain, however, has limits on attention, working memory, and the ability to make complex decisions. These limitations make parallel tasks more taxing on cognitive energy.\n\nThe AI-driven workflow removes waiting times but intensifies the mental load. Before AI, there were natural breaks that helped alleviate mental fatigue. Now, new tasks can be started almost immediately after a previous one is completed. This leads to a continuous cycle of AI-generated work feeding into the human bottleneck all day long. Research indicates that while AI speeds up software development, it also makes the work more intensive, leading to faster work patterns, taking on more tasks, and distributing work throughout the day. The shift is from creation to verification, where developers spend less time coding but more time supervising AI, checking outputs, fixing mistakes, and deciding the next steps. Productivity might have improved, but the developer experience has worsened for 27% of participants, with issues ranging from disrupted flow states to increased cognitive load.\n\nThe Harvard Business Review published an article in 2026 titled \"AI Doesn’t Reduce Work—It Intensifies It,\" highlighting similar findings. A study conducted by UC Berkeley followed employees at a tech company for eight months, revealing that 82% of participants spent less time directly writing code but more time on supervisory engineering tasks. Despite improved productivity, the share of developers reporting a worsened developer experience surged from 14% to 27%, encompassing challenges such as diminished flow state, cognitive overload, and increased likelihood of mistakes.\n\nIn conclusion, while AI accelerates work completion, it simultaneously intensifies cognitive demands, challenging the conventional eight-hour work model. The brain, much like AI, has its limits, and the increased workload and complexity of supervisory tasks indicate a potential strain on human cognitive capacities.",
  "summary": "Over the last year, I noticed something about the way I work with AI. I get much more done, but I also feel much more tired. Not “I need some coffee” tired. I mean completely mentally drained at the end of the workday, especially by the end of the week. The strange part is that I am not working more hours. AI lets me do in one hour what could easily take half a day before. That hour is just much…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}