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 recalls early Amazon days when constantly fixing problems and overworking won praise but stalled his advancement. After a decade in performance calibration meetings, he realized that being indispensable in day-to-day tasks doesn’t translate into career growth. He unpacks common “helpful” habits that actually hold you back.

• Being the go-to problem-solver at Amazon made him indispensable but stalled his promotions for years.
• Calibration panels reward people who set direction and drive broad-impact projects, not those who just execute tasks.
• Constant firefighting keeps your contributions visible only to your manager, not to senior leaders who approve promotions.
• Career growth comes from practicing strategic refusal, pushing systemic fixes, seeking visibility, and turning help into coaching so others own tasks next time.