Developer Exposes Claude Code Burnout at Major Firm
A developer's viral account reveals how a major firm's mandate to use Claude Code has forced engineers into 13-hour shifts spent merely approving AI-generated output.

An anonymous software engineer, writing under the pseudonym voxium and highlighted by researcher Simon Willison, has shared a bleak look inside a major corporation where Anthropic's Claude Code has completely taken over the development pipeline. According to the report, every single artifact in the software lifecycle—including specifications, source code, tests, product requirement documents, tickets, resolutions, and reports—is now generated entirely by the AI assistant.
The transition has reportedly created a toxic work environment where engineers from entry-level L1 to senior L7 positions are reduced to the same repetitive task: interacting with Claude Code. The developer notes that team members are forced to work 12 to 13 hours a day just to review and "press enter" on automated pull requests. Because of the sheer volume of AI-generated material, nobody on the team has the time to actually read or comprehend the code being shipped.
This shift highlights a growing disconnect between upper management and engineering realities. Leadership at the firm reportedly pressures the team to maximize output, arguing that because writing code is no longer a bottleneck, project delivery should be instantaneous. This pressure has backfired, leaving developers exhausted by the administrative overhead of managing AI agents while losing all institutional knowledge of their own codebase.
For software practitioners, this case study serves as a stark warning about the dangers of unchecked AI adoption. While tools like Claude Code promise unprecedented velocity, replacing human comprehension with automated generation can destroy developer morale and create unmaintainable codebases. It suggests that without careful guardrails, the future of software engineering risks shifting from creative problem-solving to mindless AI oversight.
This is our own summary of reporting by Simon Willison



