This article argues that AI tools speed up code delivery but raise cognitive strain, erode satisfaction, and drive developers into a cycle of nonstop, draining work. It breaks down how skipping hands-on coding reduces ownership and fulfillment, then offers steps to restore enjoyment, pride, and sustainable workflows.

• AI can cut coding time in half (4 hours → 2 hours) but leaves developers mentally drained instead of satisfied, so they skip breaks and chase the next task without ever feeling "done"
• The constant plan-generate-review loop is more cognitively taxing than writing code by hand, since reviewing/debugging AI output is draining and error-prone compared to the tactile, meditative act of writing code
• HBR frames this as "cognitive exhaustion from intensive oversight of AI agents"—workload increases in both volume and intensity
• Offloading core problem-solving to AI erodes ownership and pride in the work, making engineers feel like script managers rather than creators, even as job titles stay unchanged

The author quits a stable design-engineering role after growing frustrated with unchecked AI tools disrupting meetings, code reviews, and design processes. They trace their burnout to constant AI pressure, abandoned industry ideals, and a sense that shortcuts have overtaken craftsmanship.

• Quit a well-paying, remote, benefits-included design-engineering job despite strong performance metrics because unchecked AI adoption made the work untenable.
• Daily friction came from AI tools deployed without consent or review: auto note-takers in meetings, unverified chatbot answers in Slack, mass-merged AI-generated code, and bot-driven PR feedback replacing human collaboration.
• Frames the exhaustion using Freudenberger's definition of burnout as "political defeat" - grief over watching tech's early-2010s user-centered, civic-minded ideals get replaced by profit-chasing and political appeasement.
• Distinguishes this from ordinary overwork: the burnout stems from constantly deciding whether to push back against imposed AI shortcuts, not from hours or workload.

The article highlights a looming crisis in data engineering talent, emphasizing that the industry is failing to cultivate junior engineers needed for future demand. It critiques current hiring practices that prioritize experienced candidates while neglecting the development of entry-level roles, leading to burnout among existing engineers. Additionally, it explores the role of AI in enhancing productivity but warns against relying solely on it to address talent shortages.

• Only 2% of data engineering job postings are entry-level, while nearly 20% require six or more years of experience, choking off the talent pipeline.
• This hiring pattern, combined with burnout among existing engineers, is projected to leave 10.5 million data and analytics positions unfilled globally by 2030.
• AI boosts productivity for experienced engineers but can't replace the hands-on learning junior engineers need, risking knowledge gaps if used as a substitute for training.
• Companies need to treat AI as a collaborative tool that supports both junior and senior engineers, rather than as a fix for the talent shortage itself.