Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The "Vibe Coding" Wall of Shame

crackr.dev

Post reply on HN
Print view View original

31–40 of 88 posts

Re: The "Vibe Coding" Wall of Shame

#31

Post by g947o »

simonw wrote: post #12

Why is the LiteLLM incident on there? The linked article for that one is a 404. I didn't read any credible arguments suggesting that was caused by vibe coding. They had their PyPI publishing credentials stolen thanks to an attack against a CI tool they were using. Plus the linked article for the Amazon outage is https://d3security.com/blog/amazon-lost-6-million-orders-vib... which appears to be some other vendor prom…

My impression is that the first item on the website should be the site itself.

Barely anything on the site makes sense if you look at them closely.

We call that "slop", the last time I checked.

Re: The "Vibe Coding" Wall of Shame

#33

Post by eloisant »

bigstrat2003 wrote: post #10
doug_durham wrote: post #6

“Vibe coded”? I doubt that there is the documentary evidence that the code in these systems was never touched by a human. At best this is a list of code where AI tools were used in development. To be honest if you just created a list of all outages in all companies and systems you’d probably have a better list since AI tools are ubiquitous.

> AI tools are ubiquitous. Only among people who don't value the quality of their output. There are, fortunately, many who do value quality and are not using AI tools until they get to the point where they can usefully contribute.

Have you used a state of the art tool (e.g. Claude Code) in the past 6 months? If you only tried free tools, or only tried 1 year ago last, you really need to check again.

AI tools can absolutely contribute usefully, I can't keep count of the times where an AI pointed to an edge case I didn't think about, then helped me write the fix and the test for the issue.

I'm not vibe coding, as I'm reviewing the code, but saying they can't be useful means you haven't taken the time to look at the state of them recently.

Re: The "Vibe Coding" Wall of Shame

#35

Post by jabwd »

bluegatty wrote: post #29
jabwd wrote: post #24

Earlier quoted context omitted.

If you mean by everything "stuff that has been done before and no one cares about" then, yeah, probably. New code will still need to be written though.

No, I mean everything. It's not reasonable to suggest that AI is only going to repeat older patterns that have been trodden before, or 'things that don't matter'. AI will be writing most new code, by far. Without even getting into complicated arguments about 'creativity' - the AI is an encyclopedia of best practices, and can think a couple of steps ahead for most things you'll ever want to do. Like pro chess players…

Goodluck

Re: The "Vibe Coding" Wall of Shame

#36

Post by tonymet »

bluefirebrand wrote: post #26
tonymet wrote: post #22

AI might have been an opportunity to take engineer hubris down a knotch. Perhaps to reassess the excesses (bad performance, bad UX, poor reliability, costly development & operations, etc) . Instead of reflection, we decided to shame AI as vibe coding . How much abysmal code and products have we all shipped? Exploitative, clumsy , dangerous, vulnerable? What was our excuse? I find the entire anti-vibe coding movement…

> How much abysmal code and products have we all shipped? > We should be using it to fix all of the terrible software we’ve made over the past 20 years. Instead there are 2-3 camps. People building stuff, people hyping AI and people shaming the first 2. This seems like an odd take. The pro who are using and hyping AI are not fixing all of the crap we put out the last 20 years. They are putting the gas pedal on the am…

I don’t disagree. But what is the detractors’ goal? What will the shaming accomplish? The tools are here and can be used for good or ill.

Think about the 90s PC revolution, opening up developer opportunities. There were commercial devs and open source devs. The open source devs decided to put the new resources and tools to use to evangelize computing . And in many ways won.

We have new tools now, and can put them to good use. Moaning from the sidelines is a losing strategy.

Re: The "Vibe Coding" Wall of Shame

#37

Post by crazygringo »

Is this meaningful at all, without a control?

How often does software fail in production with human-written code? How many times has a production failure been avoided because an LLM didn't make a typo or mistake that a human would have?

This is pushing an agenda. It's not measuring anything meaningful.

Re: The "Vibe Coding" Wall of Shame

#38

Post by gobdovan »

Coding with AI is kind of like obesity in modernity: having tons of resources is the goal, but once you get there, you end up in a system you're not really adapted to.

Personally, I don't care that much about org incentives (even though they obviously matter for what OP posted) but more about what it does to my thinking. For me, actually writing code is what slows my brain down, helps me understand the problem, and helps me generate new ideas. As soon as I hand off implementation to an LLM (even if I first write a spec or model it in TLA+) my understanding drops off pretty quickly.

Re: The "Vibe Coding" Wall of Shame

#39

Post by dgb23 »

Dig1t wrote: post #13

I kind of think that the "Human Coding" Wall of Shame would be quite a bit larger and contain examples that are every bit as egregious.

I don’t think that’s the point of showcasing these issues.

The specific point is that you cannot prompt your way to reliable software (AKA vibe coding). Just as you cannot reach the same goal by glueing together stackoverflow snippets without understanding them.

Re: The "Vibe Coding" Wall of Shame

#40

Post by scientism »

g947o wrote: post #31
simonw wrote: post #12

Why is the LiteLLM incident on there? The linked article for that one is a 404. I didn't read any credible arguments suggesting that was caused by vibe coding. They had their PyPI publishing credentials stolen thanks to an attack against a CI tool they were using. Plus the linked article for the Amazon outage is https://d3security.com/blog/amazon-lost-6-million-orders-vib... which appears to be some other vendor prom…

My impression is that the first item on the website should be the site itself. Barely anything on the site makes sense if you look at them closely. We call that "slop", the last time I checked.

Indeed. The joke is that the website itself is vibe coded.
Post reply on HN