AI Coding Tools: Productivity Boost or Burnout Trap?

The promise of AI coding assistants was simple: automate the tedious parts of software development and free developers to focus on creative problem-solving. But emerging research suggests the reality is more complex, with AI potentially creating new pressures while solving old ones.

According to a comprehensive survey by Google's DORA team, 90 percent of technology professionals now use AI at work, with over 80 percent reporting productivity gains. These tools can generate code for everything from web applications to data management systems, automate testing infrastructure, and even help inexperienced developers create working prototypes through "vibe coding"—a term coined by OpenAI co-founder Andrej Karpathy for describing intentions to AI systems.

However, the productivity gains come with unexpected costs. The same DORA report found that while individual coder effectiveness increased with AI use, so did "software delivery instability"—a measure of how frequently code needed to be rolled back or patched after release to address unexpected issues. "As you use more AI, you're more likely to roll back changes that you've pushed into production," says Nathen Harvey, who leads the DORA team. "And this, obviously, is something that you want to avoid."

The pressure to move faster appears to be intensifying. A Harvard Business Review study from the University of California, Berkeley's Haas School of Business found that employees at one U.S. tech company took on more tasks, worked at a faster pace, and worked more hours after adopting AI. Even without company mandates, employees began prompting AI during lunch breaks, meetings, and other former downtimes, with some finding these periods less refreshing.

A report from Multitudes, a New Zealand-based company that tracks software engineering practices, provides quantitative evidence of this trend. Analyzing over 500 developers, they found engineers merged 27.2 percent more pull requests—packages of code approved for insertion into existing projects—but also experienced a 19.6 percent rise in "out-of-hour commits," or submissions of coding work outside ordinary schedules.

"If that out-of-hours work is going up, it's not good for the person," says Multitudes founder and CEO Lauren Peate. "It can lead to burnout."

The quality concerns extend beyond just working longer hours. Anthropic researchers found that software engineers working with a new software library performed slightly faster with AI assistance but scored 17 percent lower on knowledge assessments about the library compared to those working without AI. The biggest knowledge gaps appeared in debugging—finding and fixing code flaws.

"The goal shouldn't be to use AI to avoid cognitive effort—it should be to use AI to deepen it," says Anthropic researcher Judy Hanwen Shen.

These findings suggest a troubling dynamic: AI may be enabling developers to produce more code faster, but at the cost of deeper understanding and potentially lower quality. Some open-source projects have reported increases in low-quality, AI-generated submissions that drain core developers' time reviewing and rejecting them.

The situation reflects broader workplace pressures. Following years of industry-wide layoffs and corporate mandates for efficiency, AI deployment often comes with implicit expectations that remaining employees will "do more with less." This creates a paradox where tools meant to reduce workload may instead intensify it.

For junior developers, the implications are particularly concerning. While AI can help less experienced programmers build functional applications, overreliance may hinder the development of fundamental coding skills. Additionally, as AI enables developers to work more independently, opportunities for mentorship, skill development through collaboration, and professional networking may diminish.

The evidence suggests that AI coding tools are neither the productivity panacea nor the job-replacing threat that extreme narratives suggest. Instead, they appear to be reshaping software development in ways that amplify both its benefits and its challenges. As Nathen Harvey notes, "When you've got great things happening, and you add some AI to the mix, they're probably going to get better. And when you have painful things that are happening, [and] you add some AI to the mix, [you're] probably going to feel that pain a little bit more acutely."

The key question isn't whether AI will transform software development—that transformation is already underway. Rather, it's whether organizations can harness AI's benefits while creating structures that prevent burnout, maintain quality standards, and support developer growth in an increasingly automated landscape.