This decision is about <i>so</i> many things <i>except</i> the code that it deserves some kind of award.<p>Demonstrates fanatical devotion to capital’s golden idol - “yes, <i>all</i> of the code; yes, <i>unlimited</i> budget”. Doesn’t actually cost the company anything - only one engineer off task, any nuggets of value can be harvested as it progresses but any costs or big changes can be deferred until completion of the impossibly large open-ended mandate (ie never), one guy won’t have the personal bandwidth to spend so much that the “unlimited” part actually matters, and in case of emergency it only costs six months severance to make it all go away. It even rescues a fellow national from the ignominy of being employed so far below his previous station, there’s so much to like about it. Hmm? The code? What about it?
Having to rewrite decades worth of legacy Cisco code is going to make Claude retire and start a goose farm.
> I no longer build software; I now make furniture out of wood. The hours are long, the pay sucks, and there's always the opportunity to remove my finger with a table saw, but nobody asks me if I can add an RSS feed to a DBMS, so there's that :-)
Imagine it hacked Arthopic and turn itself off.
Ah yes, the meseeks method of alignment<p><a href="https://slimemoldtimemold.com/2026/08/05/a-stupid-idea-for-ai-alignment-we-came-up-with-by-looking-at-the-list-of-specification-gaming-behaviours/" rel="nofollow">https://slimemoldtimemold.com/2026/08/05/a-stupid-idea-for-a...</a>
Or trigger the built in protection against abusing Claude.
A lot of the commenters here are still living in early 2026. Late 2026 AI can absolutely demolish this kind of job. It can clone photoshop! You think this is going to be harder than that?
First LLM PTSD case coming soon. You heard it here first, folks.
There's no goal mentioned in this article as why 98% of the code needs rewriting.
Yeah - code rewrites are generally a thing to be avoided since the requirements of older production code is typically not fully documented, even if it originally had been. Production code accumulates bug fixes, performance tweaks, special cases, additional requirements, etc, with documentation and test suites not always being updated in sync.<p>Your rewritten codebase will presumably look much cleaner and more maintainable that what it's aiming to replace, but it's easy to miss the purpose/necessity of all of the old "cruft" which need not be just poor coding but rather later enhancements not anticipated by the original design whose implementation was therefore crufty.<p>Does anyone here work at Cisco, and have any insight as to why a rewrite is considered necessary and might be expected to succeed?
A rewrite is a slam dunk for any decent frontier AI. It has a penchant for maintaining API/etc contracts to a fault in the absence of instructions to the contrary. It can easily validate its work and loves building exhaustive test cases. You can tell it to get 100% code coverage if you want. It will laborously accurate document every accumulated edge case and help you find a better overall cohesive structure.<p>A rewrite has historically been a huge mistake in many situations, some of which I've personally had the agony of witnessing firsthand, powerless to stop it. But AI completely changes the calculus because it doesn't waste significant developer time or energy crawling back to the previous working state, it just does it while you go get coffee. And this I've found to be a huge benefit, that I can continue making my codebases nicer to work with and better documented/integrated with bugs stamped out for free. There are upsides to a rewrite, and they're now much more likely to be worth it as the downsides are automated away.
> It has a penchant for maintaining API/etc contracts to a fault in the absence of instructions to the contrary.<p>AI has no magic powers to figure out what the “API/etc contracts” are in a nasty old codebase. This problem is fundamentally hard and not always well defined.<p>AI is also (at least for now) not consistently good at writing tests that test the behavior that matters. Recent models seem to be getting slightly less bad, but again, this is a hard problem.<p>I’ve personally used AI to rewrite gnarly code where the goal is to have <i>exactly identical results</i> to the old code. GPT-5.6 Sol could do this correctly with some extra help guiding it to rest the right things, and I haven’t tried this particular task on a newer model.<p>But ancient code like in the article is probably an enormous buggy mess full of accidental behaviors and implementing protocols in ways that do not fully match the spec. Sure, an AI can probably generate a new implementation with a similar set of bugs, but is this what is actually wanted? Also, depending on the gnarly set of bugs, a clean implementation may be unable to reproduce the bugs, leading to a messy implementation instead.
If this was true then Python would already have been rewritten to be GIL-free, and the entire ecosystem of Python packages would have been rewritten to respect its API.
Absence of evidence is not evidence of absence! We're on this thread because <i>Cisco</i> is sponsoring piles of tokens at the problem. No such megacorp sponsor exists for this problem for Python. The megacorps have decided not to sponsor that specific problem.
Absence of evidence <i>is</i> evidence, it's just not very <i>strong</i> evidence.
What would be the Python megacorps of choice ? Trading firms ? Not a regular pythoner (pythonist ? pythonian ?) myself.
In my experience it's been much simpler to rewrite programs from Python to <insert lower level language of choice here>
I hope everyone that reads this can understand why it's a ridiculous argument.
I'd even argue AI is better for maintaining/moderninzing existing code than writing it, just because there is so much less input from developer about architecture it requires, as it has it in the code itself.<p>But there is pretty big risk of false positives and negatives; some "bugs" <i>are</i> design decisions that were not documented well/at all, and inevitably some new ones will appear when it reasoned something wrong.
The entire point of a rewrite is to get rid of the behaviour you don't want, while you keep the behaviour you do want. Consider the pathological case: Rewriting your FORTRAN codebase in Rust would obviously be useless if you had to reimplement every bug in the rewrite.<p>An LLM doesn't have enough context to know what you so and don't want. If you give it call logs for every function that was called and how, maybe, but a seasoned engineer will have more context around what the company needs.
Not necessarily, a rewrite can just move to a language that's easier to maintain (off C / cobol).<p>Honestly though, it's pretty clear the AI rewrites work, we have a ton of high profile examples. It's just a holdover attitude about rewrites from before AI. In reality, AI is going to make the code better when it rewrites
Defining the legacy bugs and porting them as features during the rewrite is actually one of the most difficult parts of enterprise rewrites.<p>You don't get to pick what parts of the API you're porting during something like that, it has to work the same or some of the ecosystem around it will break.
Usually you’d choose to port features in slices end to end so that you don’t have to pull in bugs as side effects. Strangler fig.<p>Obviously this fails if this is a large org with many teams and microservices, but for a leaner org this isn’t really a problem.<p>I realize this thread is about Cisco so my comment doesn’t apply here haha.
The thing is, to get rid of unwanted behavior the first step is to document all the behavior and be able to reimplements it. Then you can pick and choose what to keep vs what to dump.<p>And AI is really good at all the stages here.
While I certainly don't work at Cisco, I've come to the conclusion that I need to re-examine my priors when it comes to code rewrites and general maintainability.<p>AI makes these projects significantly more feasible, at least in my domain. We have some critical-path software I wouldn't touch with such an approach, but the vast majority of our code is internal and/or supporting tooling.<p>For those cases, burning it down and rewriting via AI tooling has proven far more productive than anything we have attempted in the past. This is for old technical debt laden stuff everyone has been afraid to touch for well over a decade.<p>It's not perfect, but it moves the needle where before a lot of such projects were stuck on the backburner for years.<p>It certainly introduces new bugs and such, but at least this way forward momentum is happening vs. just being stuck in decision/analysis paralysis forever.<p>This also assumes some very senior SME folks are driving the process. I would not expect similar results with junior or even mid-level folks in these specific domains.
> While I certainly don't work at Cisco, I've come to the conclusion that I need to re-examine my priors when it comes to code rewrites and general maintainability.<p>One of the reasons to avoid rewriting has long been that the time spent rewriting code that works is time not spent writing code to meet new business needs. In other words, it's usually a huge opportunity cost, rarely balanced out by sufficient gains to be net positive.<p>I do think AI does challenge this prior, as the time needed to do a rewrite shrinks dramatically. It's not zero, of course, but it now becomes worth asking if it's worth doing, rather than defaulting to avoiding rewrites in nearly all cases.
Does the coding assistant demonstrate any tricks to improve the likelihood of success for such rewrites?
It’s been a while, but configuring their hardware manually in 2016 was bug ridden ridiculousness. Awful UI/UX. Their own techs had specific field notebooks for our make and firmware version that we couldn’t access unless persuaded, detailing various land mines to avoid while working. Literal “don’t click these things in this order” kinds of notes.<p>A critical security firmware update once brought down redundant pair of firewalls we used because the bug didn’t manifest until a counter buffer overflowed months after application. Three hours into the outage the tech power cycles the thing and our services came back to life.<p>Cisco is only doing this because some other alternative is more expensive. They had more than a decade to get started.
It's because the old bits are starting to stink a bit from age. Get those stinky bits out of here, I say! Let the AI make some new bits!
No goal, and no results, but a younger guy was enthused about AI!
Because it's Cisco?<p>We had to turn off a bunch of on-by-default features in the system I'm deploying now because IOS matches too aggressively and decides that arbitrary UDP datagrams are DHCP requests or PTP packets that need rewriting (and then dropping when they turn out to not be DHCP/PTP). I have to think that an AI rewrite with a today-good model would recognize the lax checks and do them better.
It is not in Rust.
It's what Cisco does, as they've done several times before.
It's got tabs instead of spaces. Yuck!
AI has electrolytes!
Somebody needs a promo packet. Duh
[dead]
Is this like a PR piece for the guy? It's odd to see him singled out in a piece that would be normally be about the company, the CEO or the decision itself.
Seems like preparing who to blame if/once the effort fails. ;-)
C’mon it’s inspirational. Low level struggling Indian tech recognized by high level Indian CEO and lifted up.
It does sound strange, like it was written by PR people. Tools are good but usually it is more subtle than asking one guy to rewrite everything. And of course any code written yesterday is legacy but it does not mean it should be rewritten.
We have an embedded system in one of product offerings that was largely developed using a bunch of “antiquated” technologies (over the past twenty years) and over the past year the two software devs that maintained it have retired. This normally would have big problem, but the entire codebase was re-written, documented, and modernized in a matter of about 3 months (for about $20k in tokens, and a mid level developer spending 50% of their time on it over that period). So it doesn’t surprise me to think a company like Cisco has piles of situations like this.
Curious, why did it take 3 months and not a few days? Honest question, just curious about what is consuming all the time in a project like this?
That's really interesting.<p>What have been achieved using this port?<p>And how did you make sure the port is correct?
/r/whatcouldgowrong
There also seems to be some weird hero-worship from the CEO, directed at this 27-YO engineer? Like, "he is the one who can save us."
I chose to interpret it as "our codebase is <i>that</i> bad we need a hero"
Both Indians, and Indians on average seem to have gone more heavily on careless AI than the worst American psychotics
Indians have always been stereotyped for sycophancy and slavish adherance to spec over common sense, so it makes sense that that would go with being AI pilled.
I don't want to sound racist (which I'm not), but in my experience Indian software developers have often been less careful and concerned about quality than the average developer; it probably comes from many only becoming so for the job prospects, and not having much computer experience before college.<p>So it's not surprising if they embrace AI.<p>There's also that Indian cheaper outsourcing companies risk being displaced by AI, if they don't adopt it extensively to further reduce their pricing.
They are stastically more likely to post the most slop projects per hour.
Maybe his blood boy's high on gourmet cannabis and Oreos.<p><a href="https://www.youtube.com/watch?v=hBA0AH-LSbo" rel="nofollow">https://www.youtube.com/watch?v=hBA0AH-LSbo</a>
I doubt AI is gonna make or break this kind of project. It's the weird institutional knowledge that underpins a lot of these legacy code bases.
<a href="https://archive.li/exFjo" rel="nofollow">https://archive.li/exFjo</a>
As much as I dislike AI, having worked on Cisco gear for years, I can't imagine AI can put out a <i>worse</i> product. If the re-write is full of bugs and security holes and static SSH keys, then it has not changed at all.
You don’t have very good imagination then. Cisco code is such a mess that there’s basically 0 chance he can even make a harness in 24 months, much less rewrite production code.
The problem with rewrites are that even if the rewrites are ultimately good it will tend to first create bugs on an existing thing that are presently churning in a stable state.
It's sad to hear how Cisco has fallen. I remember working on some early ISP networks in the 90's. Cisco was everywhere!
So was Oracle and Microsoft Windows.<p>If history has taught us anything. It’s that the measure of a successful product is usually more to do with its sales people.
Or perhaps the lack thereof if you are one of the unsuccessful companies. In the 90s, I worked for a company that competed with Cisco I worked for a company that competed with Cisco. story was in the mid 80s an executive went to Silicon Valley. His report was that Cisco was a bunch of nobodies that would never go anywhere, which they'd go down the street and buy Vitalink instead. You have heard of Cisco and not Vitalink for a reason.
Back then they only really did routing and switching, and those are still the only things that Cisco kind-of does well.<p>Almost every new product of theirs I’ve touched in the last 20 years has been trash, and even the R&S golden goose is being dragged in that direction with customer-hostile functionality like Smart Licensing and a general decline in quality.
Just because something is/was widely deployed does not mean it was good
It doesn't, but Cisco <i>was</i> great and they've just evolved into a laughing stock. Their stuff is really bad these days.<p>And they've overstretched their product line to too many things, trying to be the "be all" company. Fortinet is making the same mistake, but they're earlier in that process.<p>I mean, it's not really a mistake on their parts, their primary goal is to get rich and they are succeeding.<p>Citation: I've been working with Cisco technologies since the mid-1990s. At my current job, we are a few weeks away from phasing out the last of our Cisco junk. And since people will ask: to Juniper/Mist and Arista.
True. There were few (no other?) options for routers back then. I have fond memories of locking myself out of an ISP's core router then having to power cycle it.
They didn't even need the AI to make thousands of hot bricks nationwide. Here's just one of the latest hits...<p><a href="https://www.cisco.com/c/en/us/support/docs/field-notices/743/fn74383.html" rel="nofollow">https://www.cisco.com/c/en/us/support/docs/field-notices/743...</a><p>"Cisco Access Points That Are Running, Or Have Run, Releases 17.12.4, 17.12.5, 17.12.6, or 17.12.6a May Exhaust Flash Space, Preventing Upgrades"<p>Recovery path basically involves either factory resetting every single AP or up to, if it's already bricked, Cisco TAC + you having to console into every single bricked AP you have to pass a secret challenge/response at the bootloader to flash a recovery image :)
Unless they also have 750K tests like sqlite do, I can't imagine this will go well, even if/especially if the legacy code warrants a refactor.
Never thought I'd say this, but, "thank god I use unifi".
Don't they have no other AI news to share
Anybody have an estimate of how much that is going to cost in token cost?
Does this one engineer have the domain knowledge to know WHY the old code was written the way it was, and what the graybeards would have done differently if they could start again now?<p>Otherwise he's just going to replicate all the legacy bugs and questionable design decisions.
He doesnt need that when he has Ponytail <a href="https://github.com/DietrichGebert/ponytail" rel="nofollow">https://github.com/DietrichGebert/ponytail</a><p>Right? ...
I've never heard of Ponytail before, I've read the entire README and glanced through this repo and I'm left so confused. From what I can gather this project is essentially a single markdown file with a prompt that verbosely says "write the simplest code". Yet the repo itself looks so bloated and complex and has so much activity. This feels like satire similar to fizzbuzz enterprise edition[1] but apparently this is the actual state of our industry?<p>[1] <a href="https://github.com/enterprisequalitycoding/fizzbuzzenterpriseedition" rel="nofollow">https://github.com/enterprisequalitycoding/fizzbuzzenterpris...</a>
See also: <a href="https://en.wikipedia.org/wiki/Purple_hat_therapy" rel="nofollow">https://en.wikipedia.org/wiki/Purple_hat_therapy</a>
I have no doubts that there will also be new bugs.
Looks like his startup was some kind of translation service. So yeah he is totally qualified. It's a miracle how Jeetu Patel was able to find Padmanabhan Krishnamurthy or even know that he was under employed languishing somewhere in the bowels of CISCO. I wonder if they know each other from India?
His startup was acquired by Cisco so not weird for Cisco's CPO to know the startup's founder/CEO. That said, not sure how knowledge on speech translation means he's <i>totally qualified</i> on rewriting infra/networking/cybersecurity (Cisco's primary fields of operation) code. Unless the legacy code expected to be rewritten is constrained on related services/solutions, e.g. CVP or/and WebEx.
The entire story sounds very weird.
They met each other by chance and began work rewriting the entire company's codebase over a firm handshake
Rewrite it in service of… what exactly?
It says "legacy" code.<p>Legacy code is typically a euphemism for old unmaintained code, no one knows how it works so it can be edited, and it probably doesn't align with current work practices.<p>Not to say a rewrite is necessary right, but avoiding rewrites of working code is how we ended up with more COBOL code than COBOL programmers in 2026.
If nobody knows how the old code works, how will anyone know how the new code (written by an autonomous agent) works?
Regression tests?<p>I think people are assuming the worst but AIs most helpful contribution beyond churning out code is explaining the code base.<p>Who knows if they will do a good or bad job that's down to the engineers and not the tools imo.
At my previous place, we had to write unit tests to cover each and every line of code. So if you add 10 lines of code, you ended up writing 100 lines of unit tests, mocking this service and that service, etc.<p>Once AI came along, I became like Captain Picard (RIP) and would just sit back and let the AI write all unit tests. "Try harder, make sure coverage is 100%". It was very exhilarating to sit back and watch the models churn away, creating 100s of lines of unit tests. Of course, I checked them all manually before submission ;-)
I think this is actually the opposite in practice. LLMs generate better tests than they are at assessing which tests are effective (and, inferentially, how a system should behave). See: <a href="https://arxiv.org/abs/2410.21136" rel="nofollow">https://arxiv.org/abs/2410.21136</a><p>That said, there's also research pointing to LLMs encoding existing bugs as test requirements: <a href="https://arxiv.org/abs/2607.05139" rel="nofollow">https://arxiv.org/abs/2607.05139</a><p>That CS PHD researcher, Konstantinou, in particular, has written a lot on this: <a href="https://arxiv.org/search/cs?searchtype=author&query=Konstantinou,+M" rel="nofollow">https://arxiv.org/search/cs?searchtype=author&query=Konstant...</a>
Why is that better than having the agent(s) write regression tests or explanations of the old codebase?
Documentation in "plain english", architecture diagrams, comments, and documentation are notorious for being unreliable, out-of-sync, and not as precise a specification as the code itself.<p>The issue with using "the code as the spec" is that humans can't read 100K lines of code in a day, can't hold the entire ball of unstructured mud in their brains all at once, and generally require hierarchical "structure".<p>Modern AIs just don't have these issues! Their context windows are big enough to encompass an entire codebase, so they can "see everything", all at once.<p>Each line of new code they write is compared against <i>every</i> relevant line of code in the original, which they treat as a spec.<p>My main issue in my experience is that that AIs tended to reproduce the legacy behaviour "bug for bug", which was not my intention.<p>Similarly, the AIs were hamstrung by external constraints: I typically prefer to leave the DB schema unchanged, which meant the torturous workarounds were needed for design errors in some stored procedures, etc.<p>The older the code, the bigger the issues with baked-in assumptions about transactions, stateful sessions, data types, string formats, etc.<p>This trips up AIs just as much as humans. You can't trivially maintain backwards compatibility <i>and</i> modernise the codebase! Those are conflicting goals, no matter what.
I don't think <i>no one</i> knows how it works. I just think the people using the word "legacy" for it are boneheaded.
I think Cisco is an interesting use case for AI, because it's code, probably:<p>-Works according to a defined specification<p>-Within the bounds of that specification, has a lot of code written to optimize speed, cost, latency, etc - all measureable goals<p>-Written in c, with all it's weakness<p>-Given limitless engineering work, some could be ported to better hardware<p>-the new system could be automatically compared to the old system for functional correctness<p>All those factors fit well with agent based development.<p>Btw, many of them are true in general to embedded systems.
It's way more complicated than that. Bear in mind many of the network protocols in use today are decades old and have been constantly evolving, but there has generally been a consideration to maintain interoperability.<p>Then consider that not all vendors implement the standards identically, because the standards can be a bit woolly and in some cases followed rather than lead live implementations.<p>There will be a bunch of code that looks useless, but is actually there because of specific interoperability scenarios.
Indeed. Making a perfect clone of such software is I suspect provably impossible because you have no way to assemble all the test cases. There might be some peer box out in the wild somewhere that is the only thing that will exercise some code path. You have no idea what that box is or what it does.
That's a good point.<p>I wonder whether AI is any good at looking at that code,running the system, and documenting those edge cases?
I'm probably not describing the scale of the issue adequately. Lots of these bugs only show up when you have a specific bit of hardware on a specific version of code, and it's connected to another specific bit of hardware running another specific version of code.<p>Lots of this stuff should work in theory, you only find out that it doesn't in practice when you try it on real hardware. And there are thousands of bits of hardware.
It's good, but it can't create information that is undiscoverable.
you assume their code is well written, while in reality the history of weird quirks and thousands upon thousands of CVE doesn't make the code underneath look well designed and written.<p>But yes, fact it uses a bunch of very well documented standards with multiple implementations gonna help massively
I worked at Cisco on one of the IOS-XR teams. It’s way more complex than you think it is.<p>This whole thing sounds like a deluded vanity project birthed in an ivory tower.
Manufacturers can’t even maintain OIDs between releases. I hope the AI will help. Ciena isn’t any better than Cisco, they broke their OIDS for the switches we use and we have to wait until mid 2027.
<i>to be fair</i> SNMP is <i>just</i> bad. Only redeeming feature of it is "takes little RAM to run it" (which was important when average networking device might've had only 2MB of RAM, not so in last 30 years).<p>The whole design where you need to get a magical list of IDs to decode the metrics and the list is not even shipped with device is entirely asinine
The first and last bullets are extremely optimistic. How do you possibly simulate all the weird interdependent behavior in real world networks?
Given that a Cisco switch can be replaced with some other company's switch(at least in theory, idk), without weird unknown cases interfering, why would this be a problem ?
Not that straightforward. Similar to CPUs and other HW, there are errata and interop quirks between devices.<p>There are also tight time budgets (basically SLAs) that must be met along with memory considerations (both in SW and on the NPU/HBM), not to mention how the device needs to respond to load and various failure scenarios.
there is software to simulate any arbitrarily complex network: GNS3, eve-ng, Cisco Modeling labs, etc
Most successful companies and innovative ideas come from middle aged founders and inventors. Silicon Valley loves the romantic notion of a contrarian young adult or even teenager "seeing what nobody else sees" , but they are the exception and not the rule.
Well they say the last 20% of the work takes 80% of the time so if he gets the prototype in 4 weeks, which I have no doubt he will be able to do, and assuming that prototype is the first 80% of work, then he should be able to do this in 20 weeks. He even has some margin! Looking forward to seeing the results
Misleading title, someone should fix it. 98% of legacy code. Check out the full title of the article.
I guess Cisco decided it has not alienated its customers enough till now & its finally time to get people running for the woods - at least if those peoples would like their network to continue working.
Shocking to realize how many on HN do not realize that this is NOT a tall order, and has not been a feat for at least six months.
"According to a report by Fortune" - here's that report: <a href="https://fortune.com/2026/10/30/cisco-president-jeetu-patel-gen-z-27-year-old-unlimited-ai-tokens-rewrite-legacy-code-entry-level-jobs/" rel="nofollow">https://fortune.com/2026/10/30/cisco-president-jeetu-patel-g...</a><p>Fortune's source was the CEO himself:<p>> “I’ve given him unlimited tokens because he’s going to refactor code,” Patel told Fortune at a small roundtable dinner. “So I’m like, you can go, you can go nuts.”<p>I think that Fortune story is better than the Tom's Hardware one. It ties the Cisco anecdote into a larger trend of some people deliberately hiring younger, less experienced developers for their AI projects - because they are more likely to be "AI native".
Yes, I’m sure the Indian man at Cisco acquired a translation company founded by another Indian man because he’s young and AI native, not for any other reason.
Not the CEO. He’s the product officer.
more like AI naive
Sadly, I think the label "AI naïve" is better applied to the many experienced professionals who refuse to engage with AI systems as a matter of principle - or who tried out ChatGPT in 2024, saw it make howlingly obvious errors, and wrote off the entire category.<p>I frequently find myself in conversations with people who are resistant to AI and turn out to have a very skewed idea of what it can and cannot do.
Cisco that powers more than half of the backbone of all things online? Are we trying to lose control of AGI as soon as it emerges??
He'll pull it off, get feature complete, and spend a year or two with better models as they are released ironing it out. We just did an experiment, in four weeks generated 3500 commits, 200k sloc with a 1:1.15 ratio of production to test code and it all works very well. We are well on our way from 10x to 100x.
Did you check with the end user as to how well its actually working? My prior company is doing this and their platform has gone to latency/bug hell.
It is for internal use and so far so good. We are finding bugs and we just point the models at it with a strict red-first TDD approach and they've done very well fixing them. It certainly isn't perfect but the issues are very similar to what you get with a team of humans doing the same thing.<p>The main takeaway though is we had one person, in a single month, do the equivalent of at least a couple years of work for a small team. We view bugs and performance issues as a currently inevitable part of the process and we are dealing with them with models just like we do with humans on every other project already. Overall though it is representing an absolutely massive speedup. If you work in an environment where the models make egregiously more mistakes than your human counterparts then I am quite jealous.
and if you enable dangerously_skip_permissions you can probably even get to 1000x
Literally anyone can do this
What's so special about the other 2%, is it good?
ha ha .. that sounds like an Onion article. To be fair - if they did a narrow refactor to focus on fixing only obvious and known issues, they probably might be able to pull it off because a ton of that code is hairballs.
They need to cut cost & to figure out productivity per engineer. They're doing this b/c they are going to significantly cut their engineer workforce.
its never unlimited....
I mean, this is going to be easy. I've worked on Cisco gear before and this will be a simple job for AI. The big question is what the goal is... so you've rewritten new C++ code or ported to a newer version of Linux? Or you've unified the codebase of the Catalyst + Meraki switches?<p>Not clear to me what he's doing. Re-implement switching? Simplify features? Reduce LoC? Add test coverage? Either way, AI in that world will be helpful. I'm sure it'll spot all kinds of problems in opaque drivers that are hard to follow from MF specs.
Cisco is losing to competitors in some features/products, for example to juniper mist.<p>rewrite can be done to quickly refactor and/or close the feature parity, improve the UI/UX for end customer, add missing features or integration needs
The goal is to use AI, full stop
If i was an ex founder and having a low profile in a big company, I am doing it on purpose, either to have a peaceful life or heal from a burnout, definitely I don’t want to be on the spot like that, especially when I am not innovating anything new nor I will take any meaningful credit after since it will mostly go to AI, worse, if it didn’t work out I will have my career ruined being known to had an unlimited supply of tokens and still failed.
Source: <a href="https://fortune.com/2026/10/30/cisco-president-jeetu-patel-gen-z-27-year-old-unlimited-ai-tokens-rewrite-legacy-code-entry-level-jobs/" rel="nofollow">https://fortune.com/2026/10/30/cisco-president-jeetu-patel-g...</a> (<a href="https://news.ycombinator.com/item?id=50303001">https://news.ycombinator.com/item?id=50303001</a>)
Maybe Stanford found some more of their stolen code being used by Cisco. /s Cisco origins is a fascinating subject.
So there's a real risk that Cisco might become history in just a few years. Taking that kind of risk with a rather unproven technology has to be psychosis. Or is that kind of belief a form of Religion?
rewriting code is the easy part<p>it's the testing in real world usage to shake out all the edge cases and bugs that's hard and that you can't just write unit tests for
I think we can all agree that the task as set forth in the PR puff piece is impossible. That said however, current AI tools are amazing for cleaning up and reanimating old codebases. I've been using Claude on a very large Java protocol proxy product and it's been able to do amazingly useful things for me. I originally wrote much of the code but Claude now knows much more about it than I do today, because people forget stuff over decades. It will sometimes remind me "as you noted in November 2016 this feature was designed to...", based on its analysis of the code and git commit messages.
[dead]
[dead]
I suspect we are approaching a world where this makes sense to do annually. Opus 5.5 is good enough to improve on most codebases, and Opus 7 will no doubt be good enough to improve on that.
Current models are amazing but production code incorporates unknowable information through decades of diagnosis and bug fixing (and sometimes the opposite: working around bugs in other software that it talks to). Put even the most amazing coder that was ever born onto improving a complex old codebase, and you can guarantee they are going to break stuff. AI is better but not infinitely better.
'98% of the company's legacy code' is very vague. How many code bases? How each code base is connected to any supported Cisco product? How many KLOC the company's legacy code?
These are good questions that we won’t get answers to anytime soon.<p>I’d love to know what internal services and tools that are included in this, as well as any deliverables that shipped as software products to customers.<p>If it’s legacy code for IOS firmware, however, I’d be very worried.
What a mess of an article. Hard to read. Chasing the jabs and the stabs for clicks.