logoalt Hacker News

danso • yesterday at 8:01 PM • 15 replies • view on HN

Why do people assume that this crash is the result of AI vibe coding (i.e. these companies rolling out buggy production code) versus AI-empowered vulnerability seekers? Seems more likely that a group is trying to swarm and exploit a possible vulnerability common to these banks' operations, than it is that Bank of America, Chase, and U.S. Bank all happened to roll out bad vibe code on Monday.


Replies

codingdave • yesterday at 9:21 PM

From the article: "...a technical issue at JPMorgan Chase caused ripple effects throughout the financial system."

Nobody is claiming multiple parallel failures. They are claiming one failure that impacted multiple organizations.

bdcravens • yesterday at 8:50 PM

Because people want to believe that AI code is inferior, and that it's about to go poof with a return to the previous status quo.

➕ show 12 replies
Aperocky • yesterday at 8:13 PM

The initial postmortums are out already for the 2 previous event, and they appear to have nothing to do with vulnerability.

➕ show 2 replies
fedpost • yesterday at 8:09 PM

I don't think the average person cares tbh.

It's caused my AI, it doesn't really matter who's fault it is

dclowd9901 • yesterday at 9:51 PM

The companies in question have confirmed it wasn't due to cyber attacks. That's why.

What's it going to take for the AI pushers to see that maybe this isn't the road to go down.

rs999gti • yesterday at 10:06 PM

> AI vibe coding

What's new? What has been operating fine until the AI, cloud, and centralized computing came onto the scene?

itishappy • yesterday at 8:18 PM

I'd assume that whatever happened affected a single centralized service that these banks all relied upon.

tedd4u • yesterday at 8:22 PM

Like everything else it’s probably a combination of both (as well as other causes).

bottlepalm • yesterday at 8:24 PM

Everyone is vibe coding now. It's not just you. It's not an assumption.

Vibe coding, vibe reviewing, vibe fixing. No one has a clue how software works anymore.

➕ show 1 reply
surgical_fire • yesterday at 8:57 PM

"AI cannot fail, you can only fail at AI".

Somehow I knew I would find something like this on this comment section.

Ancalagon • yesterday at 8:42 PM

Why can't it be both?

rewgs • yesterday at 10:31 PM

IMO the problem is not AI-generated code per se, but rather the utterly absurd expectations and resulting destruction of best-practices and discipline that developers all over are now dealing with.

My first thought for this week's outages has been that people are moving too fast and are, as the saying goes, breaking things.

superfrank • yesterday at 8:12 PM

Because there’s a lot of anti-ai sentiment going around right now. Blaming it on AI slop code supports pre-existing beliefs that AI is useless. If it’s AI hackers then that not only means AI is actually good at something, it’s potentially an argument for why we need increased spending and that there really is a race dynamic at play that we need to win.

Basically, blaming AI slop supports a lot of pre-existing beliefs, while blaming AI hackers does not.

➕ show 2 replies
sunbum • yesterday at 8:04 PM

Hanlons razor. “Never attribute to malice that which is adequately explained by stupidity.”

➕ show 2 replies