With an unrelenting stream of rapid AI releases—from new Gemini and Grok iterations to sudden breakthroughs hyped as AGI—many developers are experiencing acute model fatigue. Beyond the overwhelming pace of releases, developers are confronting a deeper existential question: what does it mean to be a programmer when the manual craft of writing code is no longer the primary driver of productivity?

The Identity Crisis of the Modern Coder

For many engineers, deep fulfillment historically came from the flow state of manual craftsmanship—spending hours immersed in an editor like Neovim, listening to music, and refining code by hand. However, adopting modern AI-assisted workflows requires letting go of that romanticized process. Architecture and tooling that once required weeks of painstaking, heads-down engineering can now be prompted and assembled in a matter of days. While the efficiency gains are undeniable, they render traditional manual typing skills far less valuable, sparking a sense of loss and disillusionment among veteran programmers.

Craft vs. Outcome: Navigating AI Slop

The flood of AI-generated demos often produces superficial “slop”—functional prototypes that lack genuine polish, repeatability, or real user delight. The transcript emphasizes that while AI can generate code instantly, the hardest part of software engineering remains unchanged: identifying genuine problems, understanding stakeholder needs, and building reliable, enjoyable products. Recognizing the distinction between the self-indulgence of coding for the sake of writing code and the actual objective of solving human problems helps clarify the true role of the modern developer.

Reframing the Developer Mindset

Rather than succumbing to cynicism or mourning the loss of manual coding, developers must reframe their perspective toward creative leverage. Modern AI tooling allows individual developers to tackle projects with virtually infinite scope—building security tools, automations, and enterprise-grade utilities that were previously unfeasible due to time constraints. Accepting AI is not a betrayal of the engineering ethos; it is an evolution toward focusing purely on user impact and building better tools for the world.

Mentoring question

How much of your identity as a developer is tied to the manual craft of writing code versus the value and impact of the end product, and how are you adapting that balance in the age of AI tooling?

Source: https://youtube.com/watch?v=pVMM23kUVH8&si=wWSirPdlEgh0H1qG