I'm sure the code base you were exposed to was cr-p, but you do know there is more than one product at Cisco right? And therefore more than one code base?
Clearly you don't know. IOS alone used to formally release off many hundreds of branches from one ClearCase repository and most of it's associated hardware each released off multiple branches. At one point IOS had a branch count approaching 200,000. That's why I wrote:
...but there are much larger problems that will remain, and with Cisco's branching strategy I can see whole new levels of problems being introduced.
It should have clear from my post I'm not sure how AI truly transforms one branch not to meet easy to measure metrics but actually make the code clean, understandable and maintainable, and scaling that out on all the branches of just one OS likely becomes a massive set of additional problems.
Yet you speak as if you are an authority on all products and all code at Cisco.
At Cisco I got pulled into endless projects that were collapsing across all of IOS, XE, XR and NX-OS. I know the metrics and where the bodies are buried. I never found a new and clever problem I hadn't seen before and I saw a lot of intentional problems from the trivial to the systemic which permeated every corner of every system that most people with basic skills knew not to make decades before I joined Cisco. These are why I know why the average Cisco software drone underperforms deadwood and why Cisco needs to start experimenting with fundamentally different approaches.