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

Please Do Not Vibe Fuck Up This Software

github.com

Post reply on HN
Print view View original

201–210 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#201

Post by rawoke083600 »

matt3210 wrote: post #111
rawoke083600 wrote: post #101

Been thinking of this mental model held by some "oh ai coding is always bad etc etc" (fair we all allowed opinions). But why are we okey with colleagues making from time to time terrible blunders (hey we all human ). But when ai makes mistakes its a sweeping judgment of "oh ai coding is terrible". We seen to not include all the amazing code they do right and security bugs they do find.. I feel if it was a human or co…

AI mistakes are due to pure laziness and incompetence that appears well done. There’s a big difference between that and a genuine mistake from a knowledgeable person.

Lol what ??

Re: Please Do Not Vibe Fuck Up This Software

#202

Post by vova_hn2 »

Since when github issues became a place to post a screenshot of a post from some other platform?

I've seen this behavior before only in places where people post memes and other entertainment content.

No actionable bug report/feature request. No text version. Not even a link to the original post.

Did the person who posted this mistake GitHub Issues for their personal Twitter account?

Re: Please Do Not Vibe Fuck Up This Software

#203

Post by otabdeveloper4 »

xnx wrote: post #165
otabdeveloper4 wrote: post #133

Earlier quoted context omitted.

> Why do we need AI here? AI psychosis is a real thing and an actual mental health issue.

Similar to anti-AI derangement

No. There is no "anti-AI derangement", the reaction to slop is normal.

Re: Please Do Not Vibe Fuck Up This Software

#205

Post by [deleted] »

antirez wrote: post #120

A few years ago, the probability of such shit reaching the Hacker News home page was near zero, because regardless of the merits, here was not full of normies that could not understand when a behavior is unacceptable (I'm referring to the violence of the language of the issue). And now, here we are, surrounded by people that can't tell the most obvious things.

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#206

Post by basilikum »

This is anti-AI slop. Posting a screenshot of someone else's text as an issue is about as low effort as it gets.

It's also just a completely random accusation. I experienced a bug; the software contains some amount of AI code; that must be the reason. Because there is no other way bugs are ever made. Bugs only came to life in 2023 with ChatGPT. No need to look at the actual code, see if the bug is in an AI generated part, judge the quality of the code, whether it's just large chunks of AI generated code taken as is or small parts of carefully chosen and moderated code where the AI only does busywork but the maintainer outlines the structure and understands every part of the code.

By all means, if rsync is full of low quality AI slop that causes bugs that would otherwise not exist, give some actual evidence for that and criticize it. But that is not ~~what's happening~~ what people are doing here.

Re: Please Do Not Vibe Fuck Up This Software

#207

Post by dwedge »

basilikum wrote: post #206

This is anti-AI slop. Posting a screenshot of someone else's text as an issue is about as low effort as it gets. It's also just a completely random accusation. I experienced a bug; the software contains some amount of AI code; that must be the reason. Because there is no other way bugs are ever made. Bugs only came to life in 2023 with ChatGPT. No need to look at the actual code, see if the bug is in an AI generated…

I disagree. Look at the number of recent contributions compared to the past few years, and given AI being everywhere it's reasonable to expect that it might have been directly caused by AI.

In the thread someone found the bug and it was AI generated. But even if in this case it wasn't, if the introduction of AI and bugs are correlated it's a problem even if not every bug is caused by this. Stability everywhere seems to be getting worse, we have supply chain attacks everywhere, and if the bar for stopping this is throwing out 40,000 lines of generated code and shouting "show me the evidence" for each instability, then it's time to wonder what "maintainer" means if they are no longer the ones responsible for it.

Of course the report was engagement bait, but it's useful. Before this I was not aware that I need to wonder about rsync updates and now I am. It was one of my most trusted pieces of software, and now it's not.

Re: Please Do Not Vibe Fuck Up This Software

#208

Post by nbaugh1 »

teaearlgraycold wrote: post #86
vips7L wrote: post #17

Earlier quoted context omitted.

> Like, why? Because everyone, including this forum, is addicted to the instant gratification of LLMs. It’s pure hubris of thinking you can scan the output and it does what you think it does.

TBH I don't really feel the same most of the time. I give the LLM little chunks to do. I read the code. I think. I plan. I write a bit of code. I have the LLM crunch out some bullshit task like setting up an annoying C repo. There aren't that many moments in building with LLMs where things line up so the AI can just absolutely nail some code and save me a ton of time.

I think a lot of people have a sort of “slot machine” experience with it at some point. You just start firing off prompts on some new project, wait a few seconds, see what prize you got. Then you start doing that over and over just letting the LLM code and code and not even review what it’s doing. It really is like getting hooked on gambling. You’re getting a thrill from anticipation, not the actual results.

This is what I personally consider “vibe coding”, not simply using LLMs or agents or whatever in your workflow

Re: Please Do Not Vibe Fuck Up This Software

#209

Post by dwedge »

abc123abc123 wrote: post #172

Jesus Christ... this anti-AI thing is getting ridiculous. If the code is good, bug free, and easily understood, who the f*ck cares? If a maintainer just accepts any code, without review or control, humans, just as well as "AI:s" can submit crappy code. I can only conclude that this is some kind of misplaced frustration due to job protection and feelings of insecurity that makes people this polarized and religious.

> Jesus Christ... this anti-AI thing is getting ridiculous. If the code is good, bug free, and easily understood, who the f*ck cares?

Nobody. And in that hypothetical situation that post wouldn't have been written, wouldn't have been posted to hackernews and you wouldn't have had anywhere to write this comment.

> I can only conclude that this is some kind of misplaced frustration due to job protection and feelings of insecurity that makes people this polarized and religious.

LLMs are statistical machines and revert to the mean. I suspect that people's general opinion of how good AI is at a task mostly depends on whether or not that person's ability at the same task was around average

Re: Please Do Not Vibe Fuck Up This Software

#210

Post by Diti »

netsharc wrote: post #180
Quarrel wrote: post #59

Earlier quoted context omitted.

wtf is this comment section? The author of these commits were tridge & claude. What does tridge have to do to convince the open source community that he might be a legit programmer & have a clue? Samba? Whats that? Rsync? Never heard of it. Tivo? No clue (maybe more Australian context here than others, but still). Even the comments on the github issue, are totally devoid of the context that this is a very senior open…

[flagged]

Your opinion reminds me of the narrative about cheaters in the speedrunning community. The cheaters say they cheat not because they feel superior, but because they feel “they could achieve good results if they put in the time”. They feel entitled to cheating.
Post reply on HN