From Coder to Builder: The Future of Software Engineering
Dr. Navot Akiva
2026-03-24
Discover why the future of software engineering belongs to builders. Learn how to adapt to AI coding tools, maintain ownership, and design better systems.
The technology landscape moves at a staggering pace. Recently, Boris Cherny, a key mind behind Anthropic's Claude Code, shared a highly provocative forecast. He predicted that the traditional "software engineer" title might begin to fade by the end of 2026. In his view, AI has effectively solved the raw mechanics of coding. He envisions a near future where humans transition into "builders" who direct AI agents to execute coding tasks while focusing heavily on product management and strategy.
While it might be tempting to view this forecast as an absolute certainty, it is perhaps more useful to see it as one compelling vision of where our industry is heading. It serves as a valuable signal pointing toward a major shift in how we build software.
Adaptation Over Replacement
Cherny is not forecasting the extinction of the programmer. He is highlighting a massive evolution in the daily reality of the job. The core message for computer science students is adaptation rather than replacement.
As AI takes over routine syntax generation and repetitive debugging, the value of a human developer fundamentally shifts. The industry will not need fewer technical minds. It will need technical minds capable of higher level orchestration. You are not being replaced by AI. You are being challenged to elevate your role from a purely technical executor to a strategic problem solver. The bottleneck in software development is shifting from the mechanics of writing code to the conceptual challenge of deciding exactly what to build.
The Mandate for Today: Use AI, Keep Ownership
This evolution brings a crucial mandate for today's students and professionals. You must actively integrate code assisting platforms into your daily workflow. Tools like Claude Code are becoming essential instruments of the trade.
However, delegating the typing does not mean delegating the thinking. You must maintain absolute ownership of your software. Using AI to generate code is highly efficient, but you must never blindly accept its output.
- Understand the Logic: An AI can draft a complex function in seconds, but you remain entirely responsible for its performance and security.
- Know the "Why": You need to know exactly what the code does and why it works within the broader architecture.
- Take Responsibility: If a system breaks in production, you cannot blame the AI assistant. You are the human architect holding the blueprints.
Fluency in foundational computer science principles is more important than ever. You need deep technical knowledge to audit AI outputs, catch subtle hallucinations, and optimize systems that the AI might piece together inefficiently.
How Touro GST Prepares the Modern Builder
The Graduate School of Technology at Touro University recognizes this critical pivot. The goal is no longer just to teach you a programming language. The goal is to teach you how to manage complex and AI driven systems.
The M.S. in Artificial Intelligence Systems is designed for this exact reality. The curriculum moves beyond basic programming to focus on the strategic integration of AI.
Crucially, courses like MAIN 625: AI System Design prepare you directly for this "builder" role. In MAIN 625, students learn to design and manage processes that use AI as a core component. This is taught alongside other core classes like AI Principles and Practice and The Practice of Generative AI, ensuring a comprehensive understanding of both the tools and the broader architecture.
The title on your future business card might evolve. However, the demand for visionary builders who can orchestrate AI to solve real human problems will only grow. Build your foundation, adopt the latest AI tools, and never surrender your understanding of the underlying logic.









