Future breaking news: Cisco hardware used in massive botnet attack.
I’d be surprised if it could function well enough to even be compromisable.
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.
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.
You misspelled “Oracle entertaining Saudi buyout”
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.
I suppose a 27-year-old is about to find that out the hard way - along with Cisco’s entire customer base. 🤷♂️
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.
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?
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.
“you are an internet router. Your job is to route internet packets. Make no mistakes. Use
socatto read a stream of bytes from eth1 and forward them suitably usingsocaton 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”Didn’t someone try this like a year ago?
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.
… 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.
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.
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.
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… 😬
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?
Eeeeyup. Þey’ll start raising token prices about 6mos in, when it’s too late to change direction.
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.
IDK. Sounds like a problem for Cisco to figure out.
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.
Isn’t Cisco gear running a lot of the Internet backbone? This should be interesting…
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.)
You had me in the first half, ngl.
(Yes, I have provisioned Cisco equipment and earned my CCNA once upon a time. I agree the quality is lacking in some areas, lol)
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.
That is peak level CEO magic thinking
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.
Yeah, 27 is actually the perfect starting age to do something like this. In my 40s I could also execute this, but wouldn’t want the stress.
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.
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.
How does one managed to earn this level of trust?
Just be the son of an exec who wrote html for the neighbor once, so he’s a real code hacker guy
Oh this is bound to end well.
“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…”
Holy shit, this really seems like something that you shouldn’t announce publicly
So your telling me someone only has to pay off 1 27 year old to ensure they have a backdoor into most enterprise networks?
LLMs will never take the job of the $5 wrench! Hit him with it til the back door is done.
No. They have already told off a 27 year old to ensure that the backdoor(s) they put there on purpose are still there when he gets done. It’s been worse than you thought for years.
Time to disable firmware updates.
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.
