The Emotional Shift in Tech: From Coding Passion to AI Displacement

The Emotional Shift in Tech: From Coding Passion to AI Displacement

As generative AI tools like GitHub Copilot and large language models (LLMs) increasingly automate code generation, a quiet but profound emotional shift is unfolding within the technology industry. Veteran developers who entered the field during the rise of the web—when writing Perl scripts or debugging HTML tables was a labor of love—are now grappling with a sense of displacement. Meanwhile, younger engineers, raised on AI-assisted development, often see these changes as natural progress. At the heart of this tension lies a reflection from Kellan Elliott-McCrea, a respected technologist and former Amazon executive, whose recent essay, "Code has always been the easy part," articulates a generational grief rarely voiced in corporate tech circles.

"It’s also reasonable for people who entered technology in the last couple of decades because it was good job, or because they enjoyed coding to look at this moment with a real feeling of loss," Elliott-McCrea writes. "That feeling of loss though can be hard to understand emotionally for people my age who entered tech because we were addicted to the feeling of agency it gave us." His observation cuts to the core of a cultural transformation: programming was once a craft, a personal act of creation that demanded deep engagement with logic, syntax, and system behavior. Today, that craft is being outsourced to algorithms, leaving many to wonder what remains of the artistry that once defined the profession.

The early web, as Elliott-McCrea notes, was "objectively awful as a technology." Browser incompatibilities, non-standard CSS, and the lack of debugging tools made development a frustrating, iterative ordeal. Yet, it was precisely this friction that fostered a sense of mastery. Developers didn’t just write code—they solved puzzles, hacked together workarounds, and built something from scratch with limited resources. "Genuinely amazing," he adds, because the act of creation was deeply personal. Nobody, he insists, got into web development because "programming in Perl was somehow aesthetically delightful." They did it because they felt powerful—because they could make something from nothing.

Today’s developers, by contrast, often interact with AI tools that generate entire functions from natural language prompts. While this increases productivity and lowers barriers to entry, it also risks eroding the deep, tactile understanding of code that once defined technical expertise. According to academic resources on scholarly writing from Purdue OWL, when analyzing cultural shifts, it’s essential to distinguish between surface-level change and deeper existential transformation. The move from manual coding to AI-assisted development isn’t merely a technological upgrade—it’s a redefinition of identity for a generation that equated competence with craftsmanship.

Johns Hopkins University’s guidance on avoiding plagiarism underscores the importance of context when quoting sources. Elliott-McCrea’s words gain even greater weight when viewed through this lens: his lament isn’t about resisting innovation, but about mourning the loss of a meaningful relationship with one’s work. As SFU Library’s guide on quoting notes, quotations should illuminate meaning, not replace analysis. Elliott-McCrea’s insight invites such analysis: if coding is no longer the hard part, what is? Is it now the ability to prompt, curate, and critique AI outputs? Is it ethical oversight, system design, or human-centered problem framing?

Industry leaders are beginning to respond. Companies like Google and Microsoft are redefining engineering roles to emphasize "agentic engineering"—the skill of directing AI systems rather than writing every line of code. But this transition is not seamless. For many, the emotional cost is real. The satisfaction of seeing a program run because you wrestled every bug into submission is being replaced by the quiet uncertainty of trusting an AI’s output. As one senior developer told me anonymously, "I used to feel like a builder. Now I feel like a proofreader for a robot."

As AI continues to evolve, the tech industry must confront not only the technical implications of automation but its psychological and cultural consequences. The loss Elliott-McCrea describes is not nostalgia—it’s the erosion of a craft that once gave meaning to millions of careers. Recognizing this grief is not anti-innovation; it’s essential to building a future where technology serves not just efficiency, but human dignity.