A story about Cisco handing a 27-year-old engineer an effectively unlimited artificial intelligence budget and a two-year deadline to rewrite almost all of the company’s legacy code raced across technology forums this week, becoming one of the most-discussed posts on Reddit’s r/technology community. The account describes a senior Cisco executive recruiting a former startup founder, granting him unrestricted access to AI coding tokens, and telling him, in effect, to go as far as the tools would take him — with a target of replacing roughly 98 percent of the networking giant’s older codebase within 24 months.
The claim landed at a moment when enterprise software leaders are under pressure to show that generative AI has moved past pilots and demos into work that actually changes a balance sheet. It also landed in front of an audience of working engineers who have spent two years watching AI-assisted coding tools produce impressive demos and uneven production results. The response was split almost down the middle.
What the report describes
According to the accounts circulating online, the arrangement came directly from Cisco’s president and chief product officer, who identified a young engineer who had joined the company through an acquisition of his startup. Rather than slotting him into an existing team, the executive reportedly gave him a mandate with almost no procedural constraints: pick the tools, set the pace, and spend whatever is required on model inference.
The “unlimited tokens” framing is the detail that traveled furthest. Tokens are the billing unit for large language models, and at enterprise scale a single large-scale refactoring run across millions of lines of code can cost thousands of dollars in inference alone. Removing that ceiling is a signal about priorities more than a technical decision — it tells an engineering team that compute is cheaper than engineering hours, and that the company would rather overspend on model calls than slow down.
Cisco has not published a detailed technical breakdown of the project, and several specifics that appeared in social media summaries — the exact 98 percent figure, the precise scope of “legacy code,” and the definition of completion — have not been independently confirmed. Readers should treat the headline numbers as a company-framed target rather than an audited result.
Why a rewrite is harder than it sounds
Cisco’s software estate is among the oldest and most consequential in commercial networking. Operating systems such as IOS and its successors run inside hardware that carries internet traffic for governments, hospitals, banks and carriers. Much of that code was written in C and C++ decades ago, is tuned to specific silicon, and carries behavior that downstream customers depend on in ways no specification fully captures.
That is the core of the engineering community’s skepticism. Veteran developers pointed out that the hard part of a legacy rewrite has never been typing speed. It is:
- Undocumented behavior. Old systems accumulate quirks that customers build around. Faithful reproduction requires knowing which bugs are load-bearing.
- Test coverage. A machine-generated rewrite is only as trustworthy as the test suite validating it. Legacy code frequently lacks one.
- Security surface. Networking firmware is a top-tier target. Subtle memory-handling errors introduced during translation can become exploitable vulnerabilities.
- Certification. Code shipped into regulated and government environments often carries compliance obligations that do not care how the code was produced.
Supporters of the approach made the opposite argument: that these codebases are precisely why AI tooling matters. Translating a well-understood module from an aging language into a memory-safe one is mechanical, tedious work that humans do slowly and resent doing. If models can handle the first 80 percent and engineers review the remainder, the economics change.
A broader industry pattern
The Cisco story fits a pattern visible across large technology firms through 2025 and 2026. Google has said a growing share of new code inside the company is generated with AI assistance and reviewed by engineers. Microsoft executives have made similar claims about internal repositories. Across the sector, the pitch has shifted from “AI writes snippets” to “AI performs migrations” — language upgrades, framework replacements, dependency modernization.
What distinguishes the Cisco account is the organizational choice: concentrating authority in one young engineer rather than distributing the work across established teams. That is a startup move executed inside a company with more than 90,000 employees, and it carries an obvious risk alongside the obvious speed benefit. Institutional knowledge about why a given subsystem behaves the way it does tends to live with long-tenured staff, not with the person moving fastest.
The stakes if it goes wrong
Failures in critical infrastructure software are expensive and public. The security industry has spent the past two years cataloging incidents in which a single flaw in widely deployed code cascaded outward, from large-scale government data exposures to multi-billion-dollar breaches at financial platforms. Networking equipment sits beneath all of it.
There is also a liability question that courts have barely begun to address. As AI systems take on work with real-world consequences, plaintiffs have started testing who is responsible when the output causes harm — a dynamic visible in lawsuits filed against AI developers over model-generated guidance. Code written by a model and shipped by a vendor sits in similar territory.
What to watch
The meaningful test will not be a percentage of lines converted. It will be defect rates, security advisories, and customer-reported regressions over the next several release cycles. If Cisco publishes measurable results — lines migrated, bugs found in review, vulnerabilities introduced and caught — the experiment becomes useful evidence for the rest of the industry. If it stays a story about one engineer and an unlimited budget, it remains a recruiting anecdote.
Either way, the reaction says something about where software work is heading. The debate online was not about whether AI can write code. It was about who gets to decide when that code is good enough to ship.
