AI Burnout Is Structural, Not a Tool Problem: 4-Step Fix

·

Why am I working more if AI was supposed to make coding easier?

Even today, the hand that closes the IDE at 1 AM feels heavy. Ten to twelve hours a day, six days a week, for a year and a half. The promise that AI would make coding easier has gone somewhere, and what remains in practice is a growing list of pull requests and an ever-changing list of tools. A confession posted to r/cscareerquestions by an engineer with nine years of ML experience spread quickly. The line—pressure to “work faster and more” after the shift to AI-first/AI-native—captured the felt experience of the past period exactly. Having already gone through one round of restructuring with the next round already announced, the comment that “refusing” is not an option resonates as well. This article decomposes AI burnout not as an individual willpower issue but as a practical framework of work boundaries, tool standardization, and WIP limits.

Why This Happens — Three Structural Causes

① The combination of speed pressure and layoff fear. The “AI-first” declaration is translated in practice as “faster and more.” When this is layered on top of “market anxiety with another round of restructuring already announced”, the room for individuals to refuse essentially disappears. Overtime becomes not a choice but a defensive mechanism.

② Tool learning costs offloaded to overtime. AI tools like Cursor, GitHub Copilot, and Continue.dev reduce productivity for days to weeks right after introduction. When that learning time is not counted as official work hours, it ends up absorbed as self-imposed overtime. The original post also states explicitly that “developers must constantly learn new AI dev tools”.

③ The AI version of Parkinson’s Law. Time freed up by AI is immediately filled with new work the moment it sits empty. That the original author felt “the productivity gain came not from AI but from overwork” is precisely this effect. No matter how many tools are swapped, the result is the same unless the work-volume ceiling itself is controlled.

Step 1 — Visualize: Turn ‘Felt Busyness’ into Data

The precondition for any fix is turning WIP and work hours into data. WakaTime runs automatically as an IDE plugin and records daily coding time by language. Clockify provides manual allocation by project and task, separating meetings, reviews, and coding into a visible ratio. RescueTime visualizes focus scores and fragmented time. Running these tools for just one week surfaces a distribution like “meetings 30% / coding 50% / notification checks 20%,” creating an objective baseline for improvement.

Step 2 — Standardize AI Tools and Formalize Learning Time

Constantly switching tools out of FOMO means context-switching costs erode any efficiency gains. In a team meeting, select one or two from Cursor/Copilot, and separate learning of other tools into a formal “20% slot” (weekly cap of 4 hours). The key is making the agreement with the manager explicit that “learning time is not self-development but paid work time.” If the company refuses to compensate learning time, that cost is absorbed only through personal overtime, and this asymmetry is the structural cause of AI burnout.

Step 3 — Reduce Context Switching with WIP Limits

Use the WIP limit column in Linear, Jira, or GitHub Projects to enforce a cap of 2–3 concurrent issues per person. When concurrent in-progress tasks exceed 5, effective coding time drops to half or less because of context-switching costs. WIP limits are not simply a cap on “open issue count” but a policy that intentionally breaks the combination of “reviewing PRs + coding + in meetings” to protect coding time. If work-queue wait time is metricized with OpenTelemetry, bottlenecks right before overtime can be detected early.

Step 4 — Agreement on Blocking Night and Weekend Alerts

Configure PR review bots like CodeRabbit and Sourcery, Slack, and GitHub notifications to ring only during work hours. For GitHub notifications, enable only the “Participating/Mentions” filter and switch all other repositories to “Unwatch.” Lock Slack DND from 19:00 to 09:00, and run weekend on-call voluntarily with separate compensation. Without this agreement, tool efficiency translates directly into alert fatigue, and a culture that admires “the person who replies fast” converges on notifications being always on.

Three Anti-Patterns That Must Be Removed

First, infinite AI tool collection. Trying a new tool every week lets the learning curve eat the efficiency gains. Lack of standardization is the most common technical trigger of overtime. Second, a culture that packages overtime as a signal of dedication. The original post’s report of 10–12 hours and six days a week is a clear signal of this culture. Third, a structure that nominally labels learning time as “self-development”. When the company refuses to compensate, that cost accumulates only as personal overtime.

Key Takeaway

The productivity promise of AI tools holds only under the assumption of “fixed work volume.” When an organization does not control the work scope, alert boundaries, or concurrent task count, the efficiency gained from tools is immediately absorbed into overwork. “Tool efficiency” and “work-volume control” must always move together. The answer to the question raised in the original post is not swapping tools but reaching team-level agreement on these four boundaries.

What to Do Right Now

  • Install WakaTime: Install the IDE plugin this week and run it for 7 days to output a daily coding-time report. If overtime is not visualized, there is no baseline for improvement.
  • Agree on a standard tool: In the next team meeting, agree on one of Cursor/Copilot as the standard, and formalize any learning beyond it as a “20% slot” capped at 4 hours per week.
  • Enforce WIP limits: Enable the WIP limit column in the Linear/Jira board to cap concurrent in-progress issues at 2–3. When exceeded, force new issues to “Queued.”
  • Filter GitHub notifications: Turn on only “Participating/Mentions” and switch all other repositories to “Unwatch.” Lock Slack DND from 19:00 to 09:00.
  • Agree on learning time: In the next 1:1, formalize the agreement with the manager that “learning time = paid work time.” If refused, treat that organization as a signal that it structurally maintains AI burnout in the long run.

Reference

This article was prepared with reference to the following original post: r/cscareerquestions — Why am I working more if AI was supposed to make coding easier?

Leave a Reply

Your email address will not be published. Required fields are marked *