Developers Are Exhausted by AI Coding
This web news episode discusses Brett Codes' viral video where he announces he's quitting AI-assisted coding due to mental health concerns, dependency issues, and environmental/ethical worries. The hosts explore why this resonates with developers, the pressure from management to use AI, and debate whether manual coding will become a niche artisan skill or disappear entirely.
Summary
The episode analyzes a viral YouTube video by software engineer Brett Codes (281K views in two days) where he explains his decision to stop using AI for coding. Brett initially resisted AI tools like GitHub Copilot, finding them distracting. However, he gradually adopted AI coding tools after management encouraged their use, eventually using Cursor and agentic coding extensively. His turning point came when he realized he had become dependent on AI for both work and personal decisions (asking a chatbot for medical advice during illness), lost engagement with his code, couldn't understand system intricacies without AI assistance, and became concerned about environmental impacts. The hosts note this video resonates widely because many developers have experienced similar phases of skepticism, adoption, and now exhaustion. Mike emphasizes that the real issue isn't AI itself but toxic leadership mandating AI use with implicit threats about job security, creating demoralizing pressure. The hosts debate whether hand-coded software will survive as an artisan niche (comparing to blacksmiths or handcrafted goods) or disappear entirely, concluding that coding is unlikely to become valued for craftsmanship the way other handmade products are, since code is invisible to end users. However, they acknowledge security-critical systems and ethically-driven companies might continue manual coding. Both hosts express sympathy for Brett's stand while acknowledging the realistic risk of job loss in a competitive market. They note that developer morale is at a low point due to rapid, disruptive change, with the biggest shifts occurring in the past 8 months (after Claude Opus 4.5 and similar advances). The conversation frames this as part of a broader pattern of technological tools displacing human practices, similar to TypeScript or JavaScript adoption, but with unprecedented scope affecting all languages and domains simultaneously.
About this episode
A viral video from Brett Codes has put words to something many software developers are feeling: AI coding tools may increase output, but they can also drain the joy, purpose, and understanding out of the work. Matt and Mike discuss Brett’s decision to stop using AI, the pressure developers face to adopt it, and whether writing code by hand will survive as a career - or become a niche craft.
Key Insights
- Brett Codes experienced a progression from AI skepticism to adoption to rejection, driven by realizing he had become dependent on AI for personal decisions and lost engagement with actual coding work.
- The hosts argue that the core frustration isn't AI technology itself, but leadership's aggressive mandates to use AI accompanied by implicit threats about job consequences if developers don't comply.
- Mike claims that most developers asked if they could retroactively prevent AI progress would agree to stop it, suggesting majority sentiment leans toward resistance despite perceived inevitability.
- The hosts contend that hand-coded software is unlikely to become a valued artisan niche like handcrafted goods because code is invisible to end users and businesses don't care who or what creates functional software.
- The hosts observe that manual coding may persist only in security-critical systems and ethically-driven companies, but will likely become extremely rare rather than artisanal.
- The hosts note that current developer morale is particularly low because the disruptive change has occurred very rapidly (major acceleration in the last 8 months), unlike gradual historical technological shifts.
- Both hosts express that they personally feel the tension between believing manual coding feels better for their mental health versus realistic concerns about job security and inability to find alternative employment.
- The hosts compare current AI adoption pressure to TypeScript or JavaScript adoption, but argue this shift is fundamentally different in scope because it affects all programming domains simultaneously rather than offering choice.
Topics
Transcript
All righty, everybody, this is yet another edition of the web news. And if you're watching the video version of this episode, you'll see that I have a YouTube video pulled up and it is a YouTube video that has gone pretty viral. So we are two days in according to YouTube here, and it is sits at 281 K views from a YouTuber named Brett codes. He's a YouTuber here. He also is a software engineer. Um, and the title of this video is I'm done coding with AI. And if you're not a fan of YouTube videos, he also has a blog post on his Brett codes blog, which basically goes through the same points that he's made…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
Don't Just Vibe Code, Learn While You Code
Matt and Mike discuss how junior developers can learn foundational coding skills while using AI to code, arguing that understanding core concepts remains valuable despite AI automation. They identify three learner camps (vibe coders, aspiring junior devs, and job-focused developers) and debate whether manual coding knowledge is necessary for future success in an AI-driven development landscape.
Does AGI Actually Matter to You?
The hosts discuss whether GPT-6 Astra represents AGI, concluding that AGI is a moving target with different meanings for different users. They argue that rather than a universal definition, AGI should be understood through practical application—whether an AI can perform tasks equivalent to a human professional in specific domains. The conversation emphasizes that consumer-level adoption depends more on practical capability and accessibility than on achieving theoretical AGI status.
AI Agent Skills Explained: What They Are and Which Ones to Use
Agent skills are reusable text instructions packaged in markdown files that teach AI agents how to perform specific tasks or follow processes, differing from prompts and GPTs by using progressive disclosure to avoid context bloat. The hosts discuss how skills like Grill with Docs, Wayfinder, and Code Review help structure AI workflows, emphasizing the importance of avoiding skill bloat while building reproducible processes across teams.
AI Lets Me Game More - and Work Better
Two hosts discuss how to productively spend time while AI agents run tasks, arguing that taking breaks to play retro games or relax actually improves work quality and employee satisfaction rather than cramming more work into available time. They advocate for a balanced approach that values employee wellbeing alongside productivity metrics.
How to Design Websites for Small Businesses
The episode discusses web design strategies for small to medium businesses, emphasizing that design is only part of the solution. The hosts argue that choosing the right service offering (full custom, theme-based, or pre-made) based on client needs is crucial, and that many small businesses waste money on unnecessary custom designs when templated solutions would better serve their actual business goals.