all 77 comments

sorted by: hot top controversial new old
[–] 160 points 1 week ago* (4 children)

Future breaking news: Cisco hardware used in massive botnet attack.

  • source
  • hideshow 4 child comments
  • [–] 64 points 1 week ago (1 child)

    It would genuinely be an actual achievement to make Cisco software less secure. Usually, letting AI fully write software is bad. But in this case, I expect the rewrite to be better just because of how abysmally low the bar is specifically at Cisco.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 18 points 1 week ago

    LOL! God's honest I came in to say the exact same thing! Christ, the security on that kit is miserable. I ended up buying all new routers a few years ago and now use the old ones to run the Sonos speakers at my home and studio. Anyone hacks the networks and they'll get no further than my iPods.. Have fun guys!

    Since I don't stream from the internet, its perfect.

  • source
  • parent
  • [–] 211 points 1 week ago
    [–] 93 points 1 week ago (3 children)

    Ignore, for a second, the use of AI here.

    How huge a screw up is it just to send a guy off to work on a project alone for 2 years. Can you imagine the amount of time that should be spent in code reviews looking at something someone has spent a full 2 years on? You're now going to be asking senior devs to spend months of their lives doing nothing but code reviews. And, if you skip the code reviews that's suicide.

    We all know that in 2 years Cisco is still going to be using their legacy codebase. There's not a chance in hell this will work. Just announcing this like it is a sane thing to do advertises their dysfunction.

    It's possible that he will find some low-hanging fruit and be able to rewrite some library code. But, really, when rewriting something old and bloated, the main thing you can do to add value is to remove code. And, AI agents are famous for their ability to generate vast amounts of code, not to get rid of it.

    The absolute best case here is that this guy wastes 2 years of his life, and Cisco has some kind of deal where these "unlimited AI tokens" come at some fixed price so that this project costs Cisco only $1m or so. Then, the project's a failure, they only lose a bit of money, and they can maybe learn from the experience. But, do you really make an announcement about a project that's only going to run you $1m in costs? I doubt it. This is probably Cisco setting fire to $50m or more. And, given that they announced the project like it was a good idea, can they afford to just admit it failed? With that kind of sunk cost, they're probably going to feel a lot of pressure to achieve something positive with the stunt... so something here is going to be integrated into their codebase.

  • source
  • hideshow 3 child comments
  • [–] 15 points 1 week ago

    They're advertising it trying to get some other sucker to think this will actually work and pay for enough tokens to rewrite all the code at their own company, inflating the bubble more.

    Better do it now, because in two years everyone is going to be doing it; you can get ahead of the curve! 🤮

  • source
  • parent
  • [–] 2 points 5 days ago

    That's exactly what I'm thinking.
    98% of all the legacy code of Cisco? The whole corporation? The decades of it?

    Assemble a team to do it, not just a single guy!

    People out there really thinking the answer to everything is just "more tokens"

  • source
  • parent
  • [–] 71 points 1 week ago (2 children)

    ... and suddenly, overnight, claude or whatever will have very detailed, intricate knowledge around Cisco's hardware, almost like it's regurgitating internal documentation. Hm.

  • source
  • hideshow 2 child comments
  • [–] 69 points 1 week ago

    Don't worry, guys. I am sure he adds "make no mistakes" to every prompt. No review necessary, push straight to prod.

  • source
  • [–] 66 points 1 week ago (4 children)

    What happens if the price of those tokens suddenly skyrockets because the provider now knows your entire operation is relying on this one guy vibing?

  • source
  • hideshow 4 child comments
  • [–] 6 points 1 week ago

    for all we know cisco was paid to make this announcement to inflate 'ai' valuations and IPOs, and there's no actual intent for cisco to all in on a solo dev's 'ai' rewrite.

  • source
  • parent
  • [+] -13 points 1 week ago (1 child)

    Eeeeyup. Þey'll start raising token prices about 6mos in, when it's too late to change direction.

  • source
  • parent
  • hideshow 1 child comment
  • Of course! It would be a shame to not have those tokens in the middle of your overhaul, when there's no time to pivot to another source. I'm guessing this one guy they are putting all the money on will quit once things get complicated anyway so they're probably fucked either way.

  • source
  • parent
  • [–] 61 points 1 week ago* (last edited 1 week ago) (1 child)

    I don't know... Have you provisioned Cisco equipment before? It feels like the quality can only go up.

    (But no, obviously this will end terribly unless they're incredibly careful. It's possible, but unlikely.)

  • source
  • hideshow 1 child comment
  • [–] 57 points 1 week ago (1 child)

    "Claude, rewrite all of these repos but better"

    Done, and done!

    This should be entertaining

  • source
  • hideshow 1 child comment
  • [–] 57 points 1 week ago (4 children)

    So they're replacing battle-tested unmaintainable old code written by humans with bad unreleased unmaintainable new code written by ai.

    Both are unmaintainable. What's the punch line?? Is this not the onion?

  • source
  • hideshow 4 child comments
  • [–] 1 point 17 hours ago*

    My boss did the same thing. A team of experts working on our SaaS applications for 20 years, constantly improving it to be more secure, more maintainable, more usable, more performant, better organized, better documented, more thoroughly tested, more accessible, more suited to what users needed, more adaptable, using the most appropriate technology stack, protected from various attack scenarios, fully standards compliant, efficient to deploy, etc., and we just found out he vibe-coded a total replacement in secret all on his own in a couple of months using Claude and all written in JavaScript, and he is putting it live and retiring what we built. He wasn't even going to tell us until he had migrated the last customer over to his thing, so he's been letting us all work on projects that he had no intention of using, just to buy time until his slop was done.

  • source
  • parent
  • [–] [S] 193 points 1 week ago (11 children)

    Cisco just handed a 27 year old unlimited AI tokens and the keys to 98% of its codebase. Somewhere, a senior engineer is quietly updating their resume. Rewriting code is easy. Discovering why that horrifying 1998 workaround exists is the actual final boss.

  • source
  • hideshow 11 child comments
  • [–] 53 points 1 week ago* (last edited 1 week ago) (9 children)

    Also, Cisco knows that now you can still do that. The AI market is largely subsided with VC money, so the current pieces are a fraction what they should be charging. Try this move after the bubble pops and you’ll need to pay millions for rewriting each application. If you want to vibe some slop code, now is the time.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 47 points 1 week ago (8 children)

    Yeah, I went networking to see if I could find a job. Some asshole was the keynote speaker, and his idea was that with AI, you can now just throw the requirements at the machine and have it work out perfect. And that way, at the end of the day, the artifact that's created is no longer the code, it's the product definition. That's what you gotta guard. You can just throw the code away once you're done, it's all good.

    Want to change that button's colour? Just re-create the entire fucking system, and shove it to live. Who cares how many tokens it takes?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 28 points 1 week ago (1 child)

    "you are an internet router. Your job is to route internet packets. Make no mistakes. Use socat to read a stream of bytes from eth1 and forward them suitably using socat on eth0. Use best practices. Prevent all hacks and data leaks. Eth1 is the local trusted lan. Eth0 is the wider internet. Use Claude API when confused"

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 1 week ago

    Oh wow. That's about as wasteful as burning oil to make electricity.

    And speaking of the prompt, if you want something as simple as a hello world application or Fibonacci sequence calculator, you're going to need like 10-20 sentences to explain precisely what you want. If you're also going to look at the code yourself, add another 20 lines to tell the LLM exactly how the code should look like to make maintenance easier.

  • source
  • parent
  • [–] 9 points 1 week ago (3 children)

    I warned my fellow software engineering students that this was the future back in 2006. And they believed me, but they also got really pissed.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 22 points 1 week ago (2 children)

    ... I forgot to mention one teeny part of that..

    What happens when the company providing the tokens decides that they now cost twice as much? ten times?

    Also, it's non deterministic. Good luck staying secure.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 1 week ago (1 child)

    Doesn't matter, the future of software engineering is always going to be "your boss saying into a machine what he wants", one way or another. He'll pay for it, and he'll pay for the mistakes, too, because it's always cheaper than human labour.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 11 points 1 week ago

    Yeah, absolutely. That's why when people use salesforce's easy to use flows to define business logic, they just get the business guys to do it, and they don't manage it with fleets and fleets of programmers.

    Source : Worked with salesforce as a developer, and the preference was "declarative programming" (read : flowchart diagrams) over writing Apex code,because at some point, an administrator could maintain it.

    Right? RIGHT?!

    No. At the end of the day, you're going to get a technical person to manage whatever fucking mechanism you invent, otherwise it's going to fall to pieces because some asshat can't figure out what happens on the 29th of February.

  • source
  • parent
  • [–] 72 points 1 week ago (5 children)

    Holy shit, this really seems like something that you shouldn’t announce publicly

  • source
  • hideshow 5 child comments
  • [–] 44 points 1 week ago (2 children)

    So your telling me someone only has to pay off 1 27 year old to ensure they have a backdoor into most enterprise networks?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 6 days ago* (last edited 6 days ago) (1 child)

    Time to disable firmware updates.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 6 days ago*

    Oh, the halcyon days when you could confidently check “automatic updates“ and not have to worry about anything.

    It was such a privilege when that finally became an option, and we should’ve known that they would abuse it as soon as they could.

  • source
  • parent
  • [+] 68 points 1 week ago (1 child)
  • [–] 33 points 1 week ago

    That is peak level CEO magic thinking

  • source
  • [–] 26 points 1 week ago (1 child)

    Well this is concerning. Our entire network runs Cisco.

  • source
  • hideshow 1 child comment
  • [–] 10 points 1 week ago* (last edited 5 days ago)

    It will still be "our network"... just with a wider definition of "our".

    Want to give me any pointers on what to check out first, in case there's a mad rush to join in and explore?

    Lol.

  • source
  • parent
  • [–] 25 points 1 week ago

    I think the 24 months is the scariest part. If the Eng is starting now & has 24 months, that’s one can of worms.

    If they’ve been rewriting over the last 2 years… AI has changed a lot for code writing in that time... 😬

  • source
  • [–] 25 points 1 week ago

    "Welcome back to another episode of the premier game-show of the 21st century: 'What Could Possibly Go Wrong?' Man, do we have a great one for you guys tonight..."

  • source
  • [–] 22 points 1 week ago*

    Legacy code is still around for a reason. It’s not usually just a matter of refactoring it, but the business logic tied around it all.

    Good luck lmao. Cisco will be underwater in years if they actually commit to this.

  • source
  • [–] 22 points 1 week ago (1 child)

    had founded a translation startup

    Doesn't Cisco know any networking and firmware experts, with extensive legacy code knowledge, who could vibe code through a well thought out plan?

  • source
  • hideshow 1 child comment
  • [–] 6 points 6 days ago

    Every single person who actually does work for a living at that company said no, so when the final decision maker found themselves isolated and ridiculed, they decided the collective experience of their employees was meaningless and did this.

  • source
  • parent
  • [–] 20 points 1 week ago

    Hey I'm rooting for the guy. If in two years they release this mostly generated code it should be entirely public domain. Public domain slop is better for me then hostage making spyware.

  • source
  • [–] 38 points 1 week ago (3 children)

    lol

    When I was 27 I’d been coding for 15 years, so age alone shouldn’t be the red flag.

    What is going to be a pop problem is the insane number of Chesterton fences stomped down that fuck everything over, or things that look like they can be optimized out or use cases you don’t think actually happen.

    See rust core utils for an example of extremely well trodden and well reviewed software that ran into these issues for years. Not that it’s a bad effort, it’s an inherently hard task.

  • source
  • hideshow 3 child comments
  • [–] 28 points 1 week ago (1 child)

    Hit the nail on the head there.

    Every bit of weird code the LLM wants to simplify is a workaround for some old bug.

    See also that old Joel Spolsky essay about how rewrites reimplement the bugs the legacy system fixed long ago.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 1 week ago

    Yep, rarely do devs add more code just for fun. They'll do it when the incentives are misaligned (e.g. the new modern trend of LOC changed), or doing stuff like "speed loops" to appease really shit management.

    Usually when there's some obscure extra rule in the code it's because there was some hardware fault, an undocumented use case, a complaint from a key client, or an intermittent failure.

    Anyways, I'll be sitting over here with some popcorn.

  • source
  • parent
  • [–] 15 points 6 days ago

    Leave two bullshitters in a room and they come up with this lol

    There's no way "Paddy" explains the disastrous results to Patel, who's gonna be real mad at the end of these 24 months, if not sooner, wondering where all the money went and where's the ROI.

    Truly the rule of dumb.

  • source
  • [–] 14 points 1 week ago

    Isn’t Cisco gear running a lot of the Internet backbone? This should be interesting…

  • source
  • [–] 14 points 1 week ago

    Well, let's see in what new and interesting ways Cisco software can break. Not that they needed help but it'll be fun to see this unfold.

  • source
  • [–] 10 points 1 week ago

    time to buy cisco stock, just remember to dump in about 2 months when this inevitably goes to shit

  • source
  • [–] 9 points 5 days ago

    Time to short Cisco.

  • source
  • [–] 8 points 1 week ago (1 child)

    How does one managed to earn this level of trust?

  • source
  • hideshow 1 child comment
  • [–] 7 points 1 week ago

    Oh this is bound to end well.

  • source
  • [–] 5 points 5 days ago

    Legacy code is better than vibe code code....

  • source
  • [–] 6 points 1 week ago*

    What's he gonna do for the rest of the 23 months?

  • source
  • [–] 2 points 1 week ago
    [+] 3 points 1 week ago (3 children)
  • [–] 8 points 1 week ago (1 child)

    Basically he's saying they get a blank check for AI tools.

    My understanding is this: Tokens in AI wording are essentially measurements of computational time and power. You subscribe to ChatGPT for $X and you get #Y tokens. Each prompt costs a number of tokens depending on how long it takes and how much computational power it takes. The newer and more impressive models that use newer hardware (potentially more power) and expect better results also cost more tokens.

    Basically rent a basic sedan for travel for $50 a day or a new sports car that goes faster and burns more gas and looks cooler at $500 a day. Maybe a pickup with practical hauling space for $300 a day.

    That's what people are paying for when they subscribe to ChatGPT or Anthropic. That's how those companies make money, especially at scale for large companies.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • 9 comments in c/hackernews@lemmy.bestiver.se view that post
    [–] 13 points 1 week ago (1 child)
  • [–] 11 points 1 week ago (4 children)

    There’s no way one person can understand all the things that all the code at Cisco does even at a high level.

  • source
  • hideshow 4 child comments
  • [–] 6 points 1 week ago (1 child)

    The CEO thinks this guy can optimize it all without understanding. Bon chance.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 1 week ago

    I don’t think even unlimited tokens are going to work with “rewrite this code” when the clanker literally has no idea what it does.

    His prior experience was startup for a translation app. He’s got no idea how packet switching works. Never mind the zillions of other things Cisco does

  • source
  • parent
  • [–] 2 points 17 hours ago

    Yep. Legacy code is code that has been written by people who may now be dead. It is also filled with millions of fixes to work around bugs for very specific clients.

    I hope it's a fake story because I already did that kind of task without AI and it was always a disaster. At the scale of Cisco and with AI it will be a disaster of epic proportions.

  • source
  • parent
  • [–] 4 points 1 week ago

    You can't fix IOS, Cisco. All that god awful patch work is technical debt that can never be saved. RIP

  • source
  • [–] 4 points 1 week ago

    So the other 2% are all the hardcoded admin credentials I suppose.

  • source