The impact of AI on software development has been both profound and ever-evolving. Last year, I wrote about AMD’s plans to use AI not just for generating new lines of code, but also for other steps in the software development lifecycle (SDLC), such as triaging problems, debugging code, and testing the software. At the time, we were hoping for a 25 percent productivity boost from AI use over the course of two or three years.
But with each new release, the capabilities of large language models (LLMs) improve dramatically—accelerating software development, increasing the quality of AI-generated code, and fundamentally reshaping how software is engineered. Now, just one year later, we have surpassed our productivity target, achieving a 30 percent overall productivity boost through AI. On top of that, we are rethinking not only how we use AI within the SDLC, but the structure of the SDLC itself.
We believe that the biggest AI revolution in software engineering is still ahead. So far, we have largely been teaching AI how we perform tasks and asking it to mimic existing workflows. In many ways, this constrains AI to human patterns of thinking. The next transformation will come from collaborative swarms of AI agents capable of discovering solutions independently.
Agents of today
AMD began developing AI systems for code generation, testing automation, bug analysis, and code review in 2024. At the time, our objective was to achieve 25 percent AI-generated production code by 2027 while gradually automating larger portions of the SDLC.
Measuring productivity is inherently challenging, but from the outset we have consistently tracked one objective metric: the percentage of source code generated by AI. Importantly, we count only code that passes all reviews and testing and is ultimately included in the final product. While AI-generated code is certainly not the only contributor to productivity gains, it is one of the few metrics that can be measured objectively and consistently.
By this metric, we have crossed the 20 percent mark at the beginning of this year and are now progressing towards 50 percent across entire codebase. In some software components, more than 80 percent of the code is now generated using AI.
Agentic AI has enabled us to include AI in every step of the life cycle: For code analysis and triage, agents are trained to analyze problem reports, identify and group similar requests, and highlight which code snippets are likely to need modification. For debugging and code generation, agents are directed to analyze a bug request and implement required code changes. For testing, the agents generate unit tests, and if those are passed, identify necessary integration and product-level tests. And finally, for the approval and release stage, agents prepare architecture summary, code change review, and full test results for engineers’ review and approval—and, if approved, integrate the changes into the next release.
Agents of tomorrow
Today, engineers create AI agents in their own image: They teach AI what they know about the system, how they would fix an issue, and how they would implement a change. This is already a major technological advancement. Engineers can create multiple “AI versions” of themselves, allowing these agents to work in parallel, scaling their expertise far beyond the limits of individual productivity. The limitation, however, is that these AI agents are still constrained by human thinking and human-defined approaches.
AMD
We believe the next major transformation in software engineering will occur when collaborative AI agent swarms can independently identify and develop solutions, guided by humans on what to solve rather than constrained by human assumptions about how the job should be done. Instead of providing detailed instructions on how to solve a problem, engineers will define the issue, the desired outcome, and the quality, performance, and system constraints, allowing AI agents to determine the optimal path to a solution.
A swarm of AI agents will then work in parallel to generate, evaluate, and refine multiple solution approaches. These agents will automatically validate correctness, measure performance, test trade-offs, and compare alternative implementations against defined success criteria. Finally, AI agents will prepare ranked solution options, along with validation results and performance metrics, for engineer review and approval. The agents won’t be enhancing each step of the SDLC—they will be rewriting the SDLC themselves.
To get to this point, we need to change how agents are trained. Today, improvement occurs one engineer and one agent at a time: An engineer reviews the output, refines the prompt, and repeats the process. To scale beyond this model, agents must continuously learn from one another, reuse successful strategies, and improve collaboratively across projects and teams.
We are already moving in this direction by using multi-agent workflows extensively through agentic harnesses, such as Codex and Claude Code, while simultaneously developing our own internal multi-agent systems to support the next generation of AI-driven software engineering.
A good example is our AI-driven effort to resolve issues in our Radeon Software eXperience (RSX). RSX is a user interface component that allows users to configure and monitor graphics driver behavior. In October 2025, we began using AI agents to automatically debug and fix reported RSX issues. Out-of-the-box AI tools delivered limited results, resolving only 6 percent of issues.
The percentage of software issues fixed automatically by AI agents in AMD’s Radeon Software eXperience (RSX) has been growing steadily, reaching 75 percent in June 2026.
As we analyzed failures and identified ways to improve, we built a learning loop—initially a largely manual process—to understand where the agents were falling short and how to improve them. Rather than retraining the underlying models, we refined the objectives given to the agents, allowing them to iteratively explore multiple approaches, evaluate the results against defined success criteria, and converge on better solutions. At the same time, advances in models and agent run-times further increased effectiveness. Together, these improvements significantly increased our resolution rate from 6 percent to more than 75 percent of RSX issues resolved by agentic loop.
To make agents and agent swarms truly productive, we need a continuous learning loop that feeds errors and human interventions back into future agent workflows. The opportunity is to engineer this loop around clear, measurable goals. Each cycle captures new insights, making the entire AI engineering workflow smarter and more effective. Over time, this self-reinforcing loop—not just the underlying model—will become a key driver of AI progress.
The evolving role of human engineers
At AMD, we view AI as a means of increasing productivity, improving quality, and enabling employees to focus on higher-value work. Our goal is to empower our workforce with AI, not to reduce headcount.
To support this transformation, we are investing heavily in AI education and training across the company. The way we work is evolving rapidly, and we want every AMD employee to be prepared to leverage AI confidently, responsibly, and effectively.
As AI agents continue to improve, engineers will spend less time manually implementing solutions, focusing more on defining specifications, validating outcomes, and making the strategic decisions that drive innovation.
Andrej Zdravkovic has over thirty years of experience in software development and leadership, now serving as a senior vice president at AMD. He holds bachelor and masters degrees Belgrade University in Serbia.
Facts Only
* AMD developed AI systems for code generation, testing automation, bug analysis, and code review in 2024.
* The initial objective was 25 percent AI-generated production code by 2027 and automating larger SDLC portions.
* Productivity tracking focused on the percentage of source code generated by AI that passes reviews and testing to be included in the final product.
* The metric has reached 20 percent at the beginning of the current year and is progressing toward 50 percent across entire codebases.
* In some software components, over 80 percent of code is now generated using AI.
* Agents are used for code analysis/triage, debugging/generation, unit test generation, and preparing architecture summaries for review.
* AI agents in the Radeon Software eXperience (RSX) resolved 75 percent of reported issues by June 2026 through an agentic loop refinement process.
* Improvements to the RSX resolution rate occurred by refining agent objectives rather than retraining models.
* Engineers create AI agents by teaching them system knowledge and desired solutions.
Executive Summary
The application of Artificial Intelligence in software development has led to significant productivity gains and a fundamental shift in the Software Development Lifecycle (SDLC). Initial goals sought a 25 percent productivity boost from AI over two or three years, but subsequent improvements have resulted in a 30 percent overall productivity increase. This evolution is driven by the increasing capabilities of large language models (LLMs), which are now accelerating development and improving code quality.
The progression involves moving from teaching AI to mimic human workflows to developing collaborative swarms of AI agents capable of independent solution discovery. Currently, AI agents operate across the SDLC, handling tasks such as code analysis, debugging, generating unit tests, and preparing review materials for human engineers. The next stage envisioned is autonomous agent swarms that can independently define and execute solutions based on high-level goals rather than detailed instructions.
This transformation requires changing how agents learn; moving from iterative human-agent feedback to continuous, self-reinforcing learning loops that incorporate errors and interventions across multiple agents and projects. The ultimate goal, as exemplified by AMD's work on Radeon Software eXperience, is for agent swarms to rewrite the SDLC themselves through continuous, error-informed iteration.
Full Take
The narrative outlines a transition from assistive AI, which mimics human patterns, toward autonomous, collaborative agent swarms capable of rewriting the development process itself. The critical shift is moving control from explicit, step-by-step instruction to abstract goal setting. This implies that future productivity gains will not be incremental efficiency boosts but systemic architectural changes in how software is conceived and executed.
The focus on the continuous learning loop—feeding errors back into agent workflows—points toward an emergent property of advanced AI systems: self-optimization through experience, rather than purely pre-programmed correctness. This mirrors cognitive development where iterative failure informs the next strategy. The tension lies between scaling individual expertise (multiple agents) and achieving holistic, independent problem-solving (swarm autonomy).
The implicit assumption is that human input will focus on defining the *what* (outcome, constraints) while the agents handle the *how* (implementation path), allowing engineers to transition from craftspeople executing steps to architects defining boundaries. The consequence for human agency lies in ensuring that the definition of "optimal solution" remains firmly tethered to human-defined values, preventing a drift toward purely instrumental optimization divorced from broader systemic goals.
Bridge Questions: If agent swarms can independently discover solutions guided by high-level constraints, what new forms of oversight or ethical guardrails are necessary to ensure emergent solutions align with complex, non-quantifiable human needs? How will the shift in engineer focus—from implementation details to high-level specification—redefine the necessary skill sets for future software architects? What mechanisms must be established to prevent optimization loops from creating solutions that are technically correct but strategically flawed?
Sentinel — Human
This text reads like an authoritative, internally-informed analysis blending technical progress with strategic vision, likely originating from a senior industry voice or corporate research.