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

61–70 of 88 posts

Re: The "Vibe Coding" Wall of Shame

#61

Post by tonymet »

bluefirebrand wrote: post #53
tonymet wrote: post #36

Earlier quoted context omitted.

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…

> Think about the 90s PC revolution, opening up developer opportunities I don't think the general arc of computing since the 90s has been good for humanity As a detractor, that's my goal. I want to undermine this garbage technology that is actively making life worse for the majority of people while enriching a vanishingly small segment of humans at our expense

I imagine we agree on a number of aspects .

Re: The "Vibe Coding" Wall of Shame

#63

Post by keeda »

A lot of bad software today is attributed to "vibecoding" even though these trends have been existing since before LLMs. Like, people have been complaining about Windows for decades before AI came on the scene, except these days the same issues are attributed to vibecoding.

I feel people are just lumping two things they don't like together because they are plausibly related, but without any real proven causality between them. Is this site any different?

Re: The "Vibe Coding" Wall of Shame

#64

Post by jabwd »

bluegatty wrote: post #42
jabwd wrote: post #35

Earlier quoted context omitted.

Goodluck

People riding horses in the age of automobiles are the one's who need 'luck'.

I don't remember automobiles actively harming your cognitive abilities, nor the cost increasing 5 orders of magnitude. Yet the things actively slow me down in my work by the shear impact of my coworkers using them and having to correct the many mistakes that are made. If your job was producing mediocrity, then yes, AI is awesome. Sorry for the mirror.

Edit: I have my popcorn ready for when the VC subsidies end.

Re: The "Vibe Coding" Wall of Shame

#65

Post by duxup »

keeda wrote: post #63

A lot of bad software today is attributed to "vibecoding" even though these trends have been existing since before LLMs. Like, people have been complaining about Windows for decades before AI came on the scene, except these days the same issues are attributed to vibecoding. I feel people are just lumping two things they don't like together because they are plausibly related, but without any real proven causality betw…

Can confirm, I made dumb bugs before vibe coding ... often.

Re: The "Vibe Coding" Wall of Shame

#66

Post by simonw »

mrkeen wrote: post #45
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…

> Why is the LiteLLM incident on there? The linked article for that one is a 404. -> [Endor Labs] https://www.endorlabs.com/learn/teampcp-isnt-done -> On March 24, 2026, Endor Labs identified that litellm versions 1.82.7 and 1.82.8 on PyPI contain malicious code not present in the upstream GitHub repository. litellm is a widely used open source library with over 95 million month downloads. It lets developers route re…

How does that relate to vibe coding?

Re: The "Vibe Coding" Wall of Shame

#68

Post by tonymet »

wulfstan wrote: post #49
bluefirebrand wrote: post #26

Earlier quoted context omitted.

> 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 am currently wrestling a vibe-coded codebase into a shippable state and we should call these tools out for what they actually are - technical debt generators.

do tell. why not just revibe based on the newly revealed requirements?

Re: The "Vibe Coding" Wall of Shame

#69

Post by bluegatty »

jabwd wrote: post #64
bluegatty wrote: post #42

Earlier quoted context omitted.

People riding horses in the age of automobiles are the one's who need 'luck'.

I don't remember automobiles actively harming your cognitive abilities, nor the cost increasing 5 orders of magnitude. Yet the things actively slow me down in my work by the shear impact of my coworkers using them and having to correct the many mistakes that are made. If your job was producing mediocrity, then yes, AI is awesome. Sorry for the mirror. Edit: I have my popcorn ready for when the VC subsidies end.

? 'mediocrity' ?

Do you even know what your job is?

Your job as a developer is not to produce brilliant code - it's to produce code that is so standard, disciplined, off-the-shelf and normative that it's utterly boring.

That is exactly what the AI is good at - 'the boring standard'.

-> AI is not harming anyone's cognitive abilities.

-> Cost of AI is marginal - $200/mo for a tool while devs earn >>$100K, is the cost of tires on a car

-> Token prices are dropping by 90% per year, today's AI is already pretty good, it will be a commodity soon, but we'll continue to pay probably even more than $200/mo because the value is there.

I taught myself BASIC in the 1980's and there's code I wrote in the 1990's that is literally still in production to this day. There's probably a decent chance that I've had code in production since before you were born. Over the span of those decades, it's very clear that there's a fundamental transformation, which is totally unassailable.

Re: The "Vibe Coding" Wall of Shame

#70

Post by monksy »

tayo42 wrote: post #18
bigstrat2003 wrote: post #9

Earlier quoted context omitted.

Honestly, we should shame companies for poor engineering whether humans are directly doing the work or handing it off to an LLM.

Everything is blameless, you can't do that to humans lol

You can blame humans for not caring. You can blame humans for producing a low effort.

You shouldn't blame them for things where their environment is bad, and that makes it hard to qualify when blame is unjustified.

Post reply on HN