Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

11–20 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#11
post #4

> 26k code changes in 2 months..... rsync was 67k LOC as of 236417c (latest not obviously vibecoded commit it seems?).[1] Wow. 1: https://github.com/RsyncProject/rsync/issues/929#issuecommen...

When I look at the commits themselves, most of the ones generated by Claude are testsuite changes, or at least labelled as such. https://github.com/RsyncProject/rsync/commits/master/

Is that suppose to make this better? IME the most valuable tests are those that test specific regressions. It's the scaffolding we build for ourselves to enable feature development. Remove that scaffolding and you get accidents. Pray to your god of choice these accidents don't cause harm or loss of life.

It should really be considered negligence at this point. Some of this software is extremely valuable, it's how we flourish as humans. Purposely fucking with that should bear some real world consequence. We do the same in every other industry, software is just as important too.

Re: Please Do Not Vibe Fuck Up This Software

#14
I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well?

It's like the Matrix, with the little rant about the primitive human minds not being able to accept paradise. You wrote the perfect tool, you won, almost undisplaceable in a niche, reliable, a metaphorical household name. It makes no sense to anyone to gamble or mess with that, it's just mind boggling.

And that's still a damn obnoxious thing to do in the formal issue tracker. Bad attitude, bad faith.

Re: Please Do Not Vibe Fuck Up This Software

#16

I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well? It's like the Matrix, with the little rant…

Are you basing this opinion on the issue or actual evidence? Because this github link, although interesting, is almost completely context free on what the drama is beyond "Claude". The rsync maintainers could be anywhere on the spectrum from the perfect and responsible maintainer to incompetent children and we couldn't really tell.

Re: Please Do Not Vibe Fuck Up This Software

#17

I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well? It's like the Matrix, with the little rant…

> 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.

Re: Please Do Not Vibe Fuck Up This Software

#18
post #13

[flagged]

The comments are definitely not worth reading. It’s a very sad thread, you literally had to go through all of them to find one that wasn’t about hate and stating some facts about the issues of the code.

I found them worth reading for the following set of thoughts came up:

- programmers had problems with delivering quality long before LLM’s

- very much research and tools went into that, bringing us {Git, libraries, VSCode, reviews, …,} but the human factor stayed the same (and more pronounced imho than in other fields of engineering)

- LLMs democratized programming, enhancing a few, dropping the bottom to no skill programming

- the tools and practices created for the quality problems from the past turn out to be wholly incapable of maintaining quality in the present

The main problem behind this is that those delivering the QA tools of the past are central in the AI race. Old school engineering would separate these concerns.

Re: Please Do Not Vibe Fuck Up This Software

#19
post #4

> 26k code changes in 2 months..... rsync was 67k LOC as of 236417c (latest not obviously vibecoded commit it seems?).[1] Wow. 1: https://github.com/RsyncProject/rsync/issues/929#issuecommen...

When I look at the commits themselves, most of the ones generated by Claude are testsuite changes, or at least labelled as such. https://github.com/RsyncProject/rsync/commits/master/

Aren’t LLMs notorious for just making tests pass and not actually testing functionality?

Re: Please Do Not Vibe Fuck Up This Software

#20

[flagged]

If I were a user, knowing that the maintainers just let Claude lose on rsync would be bad for my stress levels.

In any case, I hate rsync owing to how easy it is to accidentally deleting everything. From my pov I don't care if it disappears.

Post reply on HN