In the ongoing debate about how artificial intelligence will reshape software development, one of the boldest voices belongs to Boris Cherny, creator of the AI coding agent Claude Code. After previously declaring that traditional software engineering as a job title is on its way out, he is now turning attention to the tools that have defined the profession for decades. According to his view, familiar coding environments such as graphical IDEs and code editors could soon give way to AI-driven workflows that radically change how software is built.
Cherny argues that as AI agents become more capable, they will increasingly own the full development lifecycle, from writing code and tests to wiring services together and handling deployment. In this scenario, classic integrated development environments are no longer the central hub of activity; instead, AI systems operate closer to the terminal and infrastructure, automating tasks that once required human navigation through complex tooling. The decision to center Claude Code around the terminal reflects this philosophy, treating it as the lowest common denominator across teams that currently rely on a wide range of editors and IDEs.
Behind this prediction is a broader thesis about the evolution of the software engineering role. Cherny has suggested that AI has “practically solved coding,” at least for many of the routine tasks that used to consume engineers’ time. As a result, he believes the traditional software engineer title will begin to fade and be replaced by something closer to “builder” – a professional who orchestrates AI agents, defines problems, and sets direction rather than writing every line of code manually.
This vision does not mean humans disappear from the development process. Instead, the human role shifts toward higher-level responsibilities such as system architecture, product thinking, quality oversight, and strategic decision-making. Anthropic’s internal data suggests that while engineers already rely on AI for a significant portion of their work, only a minority of tasks are fully delegated end-to-end, which keeps people firmly in the loop as reviewers and decision-makers. The emerging challenge is less about having nothing to do, and more about redefining what meaningful, high-impact work looks like in an AI-heavy environment.
Cherny acknowledges that this transition is likely to be uncomfortable, especially for professionals whose identity has been closely tied to specific tools or coding practices. As AI systems accelerate and expand their capabilities, some established workflows and skill sets may feel suddenly outdated. His advice to developers and other knowledge workers is to experiment early, stay curious, and avoid waiting for a “stable” new normal that may never arrive. Those who are willing to adapt, learn new abstractions, and collaborate with AI tools are better positioned to shape the next phase of the industry.
The implications of this shift extend beyond software engineering. If AI agents can take over much of the hands-on execution in coding, similar patterns may emerge in other white-collar domains where work happens on a computer. Roles could move away from narrow task execution and toward orchestration, judgment, and integration of AI capabilities into real-world outcomes. That makes the current conversation about coding tools a proxy for a much larger question: how work will be organized when intelligent systems are embedded in everyday tools and workflows.
Cherny also emphasizes that the direction of this transformation should not be left to any single company or product. He frames it as a societal conversation about how to balance productivity gains, job quality, and long-term opportunity as AI becomes more powerful. While the exact timeline for the decline of traditional coding tools is still uncertain, the underlying signal is clear: developers and leaders alike need to plan for a future where AI is not an add-on, but a central collaborator in building software.
Read more such articles from our Newsletter here.
