AI Coding Makes Development Easier - So Why Are We Burning Out?
Hosts discuss how AI coding tools, while making development easier, are paradoxically causing burnout by eliminating the struggle-and-satisfaction cycle that previously sustained developer motivation. They explore the psychological toll of AI-assisted work where accomplishment feels hollow and recommend finding personal projects and adjusting workflows to maintain job satisfaction.
Summary
The episode explores the unexpected psychological downsides of AI-assisted coding despite its productivity benefits. Mike and the hosts note that while AI tools dramatically reduce the time and effort needed to build software, developers are experiencing a peculiar burnout pattern: there's less struggle but also less satisfaction at completion, since the AI did most of the work rather than the developer themselves.
The speakers reference a viral tweet from Dylan Milroy, a principal engineer at Cloudflare, expressing difficulty finding joy in building with AI compared to the pre-AI era when solving hard problems manually provided a distinct endorphin rush and sense of accomplishment. The hosts resonate with this observation—previously, frustration during problem-solving was balanced by peak satisfaction when solved. Now, with AI handling most tasks, there's either frustration or numbness, with no satisfying payoff.
A key insight is that the journey has become too short. Where developers might spend two hours methodically setting up complex infrastructure, AI now does it in 15 minutes, leaving the developer waiting or context-switching rather than immersed in focused work. This rapid task completion, combined with constant context-switching between multiple parallel AI agents, creates cognitive drain without the reward that justified the struggle before.
The hosts discuss how discovering new AI workflows initially provided satisfaction, but that satisfaction disappears on repetition once the workflow is mastered. Mike discovered he could SSH AI into servers to set up entire Docker stacks, which felt exciting the first time but lost all appeal by the second implementation because it became automated and predictable.
They examine the philosophical question of ownership: if AI writes the code based on your prompts, did you really build it? The hosts draw parallels to WordPress themes and managers directing teams—acknowledging these are tools and delegation, yet noting that the satisfaction differs fundamentally when you're simply prompting rather than engaging with the material.
The conversation shifts to systemic pressure: CEOs across industries are becoming 'AI-pilled,' creating a culture where developers must embrace AI tools or risk being seen as obsolete. This forces developers to participate in a system that's causing their burnout while having little choice to opt out.
Mike proposes solutions based on personal experience: (1) finding passion projects unrelated to work code—he created a small elevator-operator game using AI that provided genuine satisfaction because it was creative, had clear design goals, and received positive feedback from players; (2) trusting AI more by reducing exhausting code reviews, instead relying on comprehensive testing and manual QA workflows; (3) seeking projects with real-world impact and user feedback rather than internal/beta work.
The hosts acknowledge these solutions are partial and individualized. They emphasize that developers must actively seek ways to derive satisfaction from work, whether through personal projects, finding meaningful user feedback, or restructuring workflows to reduce draining tasks like comprehensive code review. Without deliberately addressing this burnout source, developers may exit the profession entirely.
About this episode
AI makes development faster and easier - but does it also make the work less fulfilling? Matt and Mike discuss AI coding, developer burnout, context switching, code review fatigue, and how developers can find a healthier balance.
Key Insights
- Developers previously experienced satisfying endorphin peaks when solving difficult problems after sustained struggle, but AI-assisted development eliminates the struggle without providing equivalent satisfaction at completion, leaving only numbness or frustration.
- The journey from problem to solution has become so abbreviated—from hours to minutes—that developers experience cognitive drain from context-switching and waiting rather than the focused, immersive work that previously justified the effort.
- Discovery of new AI workflows provides initial satisfaction, but that satisfaction immediately disappears upon repetition because the workflow becomes automated and predictable, creating a shrinking pool of new discoveries to sustain motivation.
- Developers question whether they actually authored code when AI generated it from their prompts, creating a sense of hollow achievement even when work is completed, as opposed to the tangible satisfaction of personal struggle and mastery.
- CEOs across industries have developed nearly identical messaging that developers must adopt AI or become irrelevant to the company's future, forcing participation in a system causing burnout with little option to opt out.
- Code review, which already increases as developers advance in their careers, has become exponentially more draining with AI because reviewers must scrutinize far greater volumes of code without corresponding increases in time or cognitive capacity.
- Projects with user impact and real-world feedback provide significantly more satisfaction than internal tools and beta features, even when AI-assisted, suggesting that visibility and validation matter more to burnout prevention than the tool used.
- The elevator-operator game Mike created using AI provided genuine satisfaction because it combined AI assistance with creative design ownership, user feedback, and clear design iteration—suggesting burnout mitigation requires actively structuring work to include these elements.
Topics
Transcript
Today, we're going to be talking about the human element of AI coding. More specifically, we're going to be talking about the effects of it. Because it's kind of weird, right? We go to start a project, we're like, hey, I'm going to go start this golf app, or I'm going to go start this little system utility for myself. And in the past, we'd be Googling and checking into things, and we'd engineer it ourselves for the most part, unless a piece of software already existed. But now we just kind of prompted into existence. We more or less say to almost a digital employee, really, hey, I want this thing. This is how I want it. Maybe there's…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
Kimi K3 Brings Frontier AI Into the Open
Kimi K3, a new 3 trillion parameter open-source AI model, represents a major advancement in frontier AI that rivals closed-source models like GPT-5.6 and Claude Opus. While offering exciting possibilities for corporations to run powerful AI locally without subscription costs, it poses significant safety risks by allowing malicious actors and state entities to deploy unrestricted AI systems without safety guardrails.
JavaScript Isn't Always the Answer: Native Browser Features Every Developer Should Know
This episode discusses how modern browsers have evolved to handle features that previously required JavaScript or Flash, such as form validation, accordions, dialogs, popovers, and responsive images. The hosts argue for using native browser APIs and semantic HTML instead of over-engineering with JavaScript, which reduces code complexity, improves performance, and enhances accessibility.
Growing Your App: From MVP to MLP
The episode discusses the distinction between MVP (Minimum Viable Product) and MLP (Minimal Lovable Product), using a golf score-tracking app as a case study. The hosts argue that building too many features due to AI-enabled development can complicate products unnecessarily, and emphasize the importance of user feedback, gut instinct, and resilience when determining what features actually make a product worth using.
What Happens When Physical Games Disappear?
The speakers discuss Sony's decision to end physical disc production for PlayStation games by 2028, exploring the cultural impact beyond ownership and preservation concerns. They debate whether eliminating physical media removes an important part of gaming culture that supports both collectors and the broader gaming industry, using an audiophile-to-consumer market analogy.
AI Safety: From Narrow AI to Superintelligence
This podcast episode explores AI safety from narrow AI through superintelligence, discussing how current AI systems are progressing toward artificial general intelligence (AGI) and potentially superintelligence (ASI). The hosts examine the risks, alignment challenges, and governance issues that arise at each stage, while acknowledging both the theoretical nature of these predictions and the need for proactive safety measures.