Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

381–390 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#381
post #380

Earlier quoted context omitted.

Yes. That's called firing the customer in my line of work. This doesn't seem egregious enough to fire the customer.

Again, this is not work and they are not customers. This is somebody spending their free time on code they enjoy and then putting the result online. The reason businesses are careful about which customers they fire is because they want to keep having customers. Open source maintainers have no reason to deal with that shit.

Then he can fire the customer. By simply closing the issue.

Re: Please Do Not Vibe Fuck Up This Software

#382
post #158

Earlier quoted context omitted.

[flagged]

I'm not sure how to interpret your comment. It could be - a response to my comment saying that I am "illiterate" and cannot differentiate LLM output vs actual human comments (in that case I'm not sure what you're adding to the discussion here beyond a personal attack) - a general comment saying it's getting harder for people in a position similar to us (i.e. tech / tech-adjacent who interact a lot with others who wri…

It was a general comment. Sorry for being unclear. I'm very bothered by hearing this exact thing a lot lately.

It's something I'm racking my brains over, how some people can tell certain things and intentions apart and others cannot - and how that set is different for everyone, and how this "flaw" is currently causing a lot of trouble because we, collectively, are not very well practiced in detecting this kind of thing.

I don't think the internet is dead just yet, because I don't think anybody truly has the concrete intention to destroy all knowledge.

Re: Please Do Not Vibe Fuck Up This Software

#383
post #346

Earlier quoted context omitted.

Look, it's not that long time ago when we had the xz malware. The pattern is always the same. Maintainer of the project is doing X, people start to pressure them to do something else, maintainer gives up and opens the project up to other maintainers, and then many things can happen. If there is any lesson from the incident, open source maintainers should never allow the pressure to happen, ignore it if it's too stron…

If I were the rsync maintainer I’d probably set the repo to only allow issues and PRs from prior contributors until people learn to behave.

If I were the rsync maintainer after this I'd unpublish it everywhere I had control over, delete the repo and turn off my computer to go walk in the park. The linked thread is insane.

Re: Please Do Not Vibe Fuck Up This Software

#384
post #367

Earlier quoted context omitted.

> and grasp at every straw to combat it, which is a sane response Attacking every open source maintainer who might use AI for the sin of having used AI because one hates AI is just abusive behavior, not "sane response". What would the "sane response" be for people tired of the "AI is being forced down my throat and I need to combat it by attacking open source maintainers" side? Grasp at every straw to combat such beh…

> Attacking every open source maintainer who might use AI for the sin of having used AI because one hates AI is just abusive behavior, not "sane response". That's not what happened, and I think you know it. The number of LOC introduced in the last 2 versions of rsync is off the charts. And there are bugs. I've been in a situation like the author of that issue. Upgrade a package and things fall apart and it would be v…

The absolute bulk of the LOC introduced are docs and a unit test system. Let's not just make stuff up now.

Re: Please Do Not Vibe Fuck Up This Software

#385
post #125

Earlier quoted context omitted.

> I think this behavior is very silly and people are just trying to justify their hate to AI by latching onto every possible thing It's not silly to have issues with something. People act on their issues. Possibly not the issue underlying the commit at hand here but something else, and act on it which makes it something to consider. My guess is people are tired of the "AI is the greatest thing since [cultural referen…

> and grasp at every straw to combat it, which is a sane response Attacking every open source maintainer who might use AI for the sin of having used AI because one hates AI is just abusive behavior, not "sane response". What would the "sane response" be for people tired of the "AI is being forced down my throat and I need to combat it by attacking open source maintainers" side? Grasp at every straw to combat such beh…

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#386
post #161

Earlier quoted context omitted.

A couple years back, I think I would have bent over backwards to defend the maintainers. It is a gruelling and thankless effort to maintain any open source project, let alone one as established as rsync. I guess I just don't see AI being a net positive anywhere, and I have to see this backlash to using gen AI as a good course correction from the general populous. There are other posts talking about the instant gratif…

> instant gratification I'm with you. I don't understand why it affects some people more than others. To me, using AI triggered my sense for drugs and addiction after a while: when your first association for an engineering product is "it feels _great_!" then run, it's just cocaine with extra components. A tool should not make you feel good, just accomplish the task.

ADHD might be in play, and I think it‘s undiagnosed by more people than we assume. And it‘s fine, because as long as you can deal with it, it‘s not an issue. I can imagine that the addiction to LLM hits the same areas as addiction to, say, gambling, binge eating or shopping. I wrote a small thing about it here:

https://news.ycombinator.com/item?id=48081469

Re: Please Do Not Vibe Fuck Up This Software

#387

Seem to me some people have forgotten about FOSS projects > 15. Disclaimer of Warranty. > THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FI…

Here's the OSS users disclaimer:

I RESERVE THE RIGHT TO COMPLAIN, WHINGE, CRITIQUE, GET MAD AT, OR OTHERWISE COMMENT ON ANY AND DECISIONS, COMMITS, PATCHES, MARKETING, OR OTHER DECISIONS MADE BY THE PROJECT. THESE COMMENTS COME WTH NO WARRANTY FOR FITNESS FOR ANY PURPOSE, INCLUDING THE IMPLIED WARRANTY OF BEING CORRECT, USEFUL, OR KIND. SHOULD MY COMMENTS PROVE UNWANTED, YOU RESERVE THE RIGHT TO STICK IT WHERE THE SUN DON'T SHINE.

Feel free to print out this disclaimer so you have a copy to reference whenever you come across unwanted criticism of a foss project.

I really don't get how people don't realize that this "they can do whatever they want" stance cuts both ways. Users can do whatever they want as well. If they don't like something, they can express it...

Re: Please Do Not Vibe Fuck Up This Software

#388
post #383
post #346

Earlier quoted context omitted.

If I were the rsync maintainer I’d probably set the repo to only allow issues and PRs from prior contributors until people learn to behave.

If I were the rsync maintainer after this I'd unpublish it everywhere I had control over, delete the repo and turn off my computer to go walk in the park. The linked thread is insane.

Just going away from computers for a few days should be enough, the mob will get tired soon.

Re: Please Do Not Vibe Fuck Up This Software

#389

Earlier quoted context omitted.

it's dangerous to refuse to understand whats happening broadly, and what's taking place in this thread, and to signal that it's ok to keep refusing to understand it. the anger that's showing up around ai isn't a matter of the masses being misinformed, or the messaging around it, it's a matter of physics. you have this one thing that is being used as an excuse to lay people off en masse, you have tech ceos near daily…

If you think you're owed a salary to do something that a simple machine can do, I have a field for you to plow by hand.

Replace the C-suite with the chatbots first.

Re: Please Do Not Vibe Fuck Up This Software

#390

Earlier quoted context omitted.

This is rsync we are talking about. A bug in rsync basically means lost data and/or unreliable backups. I think it's normal to be pissed at lost data. Maybe it's not socially acceptable to spit in the face of a volunteer but it's 100% human to feel annoyed by an obvious drop in code quality.

The thing is, showing the annoyance to the volunteer, who is already doing their best, has two possible outcomes: 1) they stop volunteering 2) they will ignore you In neither of that is your issue solved. So maybe it's better to deal with the frustration on your own and then file a bug report.

If committing thousands of lines of unreviewed AI generated code is "doing their best", I'd argue that them not contributing anymore would be a net benefit for the project.
Post reply on HN