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

21–30 of 88 posts

Re: The "Vibe Coding" Wall of Shame

#21

Post by bluegatty »

porcoda wrote: post #11

In my experience over the last couple years, lists like this won’t move the needle at all. The AI zealots reject anything that calls into question the AI stuff, usually appealing to “just wait, better models/agents/guardrails imminent” and claiming that anecdotal productivity gains are worth the risk. The people concerned about AI already are concerned and just fall back to “I told you so”. Unfortunately the decision…

If by 'zealots' you mean the vast majority of developers, who are using AI tools in one way or another.

The AI is already substantially better than most humans for a huge spectrum of at least narrow tasks. Those 'skills' will expand in scope, the evidence is overwhelming and unequivocal.

Within 12 months it will be considered a 'security concern' to not have AI at least to some degree of autonomous review.

It's very easy to overstate the impact of AI (and sometimes it's annoying), but it's just unreasonable to be in 'denial' at this stage.

The only concern really is how, when, and with what kind of oversight we use the new tools - that that 'they are used'.

Re: The "Vibe Coding" Wall of Shame

#22

Post by tonymet »

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 to be terribly tacky and judgmental.

We have an incredible tool that could 10-100x productivity. 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.

Sad, really.

Re: The "Vibe Coding" Wall of Shame

#24

Post by jabwd »

bluegatty wrote: post #15

'vibe coding' is too loose a term. Everything will be generated by AI in the very near future, and it will range from 'fancy auto complete' to 'entirely autonomously generated' with many nuances and subtleties in between.

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.

Re: The "Vibe Coding" Wall of Shame

#25

Post by joe_mamba »

Thorrez wrote: post #7

For CVE-2026-0755, that's a vulnerability in gemini-mcp-tool. gemini-mcp-tool's Github repo says "This is an unofficial, third-party tool and is not affiliated with, endorsed, or sponsored by Google." but this list shows the Google logo next to the vulnerability. Also, it's not entirely obvious to me that the vulnerability was introduced by vibe coding. https://github.com/jamubc/gemini-mcp-tool Disclosure: I work at…

>Also, it's not entirely obvious to me that the vulnerability was introduced by vibe coding.

IDK why people act as if vibe coding invented software bugs that lead to vulnerabilities, as if those weren't already a thing by human programmers.

Re: The "Vibe Coding" Wall of Shame

#26

Post by bluefirebrand »

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 amount of crap being shipped

I don't think anyone except the most die hard AI lovers truly believe is producing high quality work on the balance. It is absolutely producing more but worse output than we've ever seen before

Even if it is capable of producing high quality work, you have to realize that most people using it are not capable of getting it to produce work of that quality. Nor do they seem to really care to

Re: The "Vibe Coding" Wall of Shame

#28

Post by g947o »

Thorrez wrote: post #7

For CVE-2026-0755, that's a vulnerability in gemini-mcp-tool. gemini-mcp-tool's Github repo says "This is an unofficial, third-party tool and is not affiliated with, endorsed, or sponsored by Google." but this list shows the Google logo next to the vulnerability. Also, it's not entirely obvious to me that the vulnerability was introduced by vibe coding. https://github.com/jamubc/gemini-mcp-tool Disclosure: I work at…

The first link claims the 6-hour outage wiped 99% of order volume. I went to the "source" and found an (AI generated?) ad by a company that wants to sell a product, where I cannot find the 99% number.

This whole website and everything around it are almost ironic.

Re: The "Vibe Coding" Wall of Shame

#29

Post by bluegatty »

jabwd wrote: post #24
bluegatty wrote: post #15

'vibe coding' is too loose a term. Everything will be generated by AI in the very near future, and it will range from 'fancy auto complete' to 'entirely autonomously generated' with many nuances and subtleties in between.

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 thinking they're going to beat the algo with some kind of fancy human creativity.

Developers roles are changing, very fundamentally, you're now 1/2 a layer of abstraction above the code, and you're not going to writing it better than AI (in most cases) any more than a human will be better at sawing wood than the power tools. And yet, carpenters still exist.

Re: The "Vibe Coding" Wall of Shame

#30

Post by simonw »

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.

> Only among people who don't value the quality of their output.

I value the quality of my output and I make extensive use of AI tools.

That's why the original definition of "vibe coding" is useful: creating code with AI tools without reviewing or caring about the quality of that code.

It's also possible to use AI tools as part of a responsible engineering process that is intended to produce production quality software.

Post reply on HN