Live data from Hacker News

Did Claude increase bugs in rsync?

alexispurslane.github.io

311–320 of 611 posts

Re: Did Claude increase bugs in rsync?

#311
post #305

Earlier quoted context omitted.

He can't make the evidence of absence claim, but he can absolutely make the absence of evidence claim.

Perhaps in an “everyday language” way, but not in the technical, statistical sense. In an underpowered statistical study, a claim that two experimental conditions did not differ are not persuasive.

No. It's a description of the result of the maybe underpowered study. the underpowered study did not find evidence. Evidence is absent. Because it is underpowered, it's not evidence that the effect is absent.

The claim is not "two experimental conditions did not differ". The claim is "The data do not show evidence that the experimental conditions did differ".

Re: Did Claude increase bugs in rsync?

#313

Earlier quoted context omitted.

Seems like someone could use Claude to port rsync to Rust and the whole enterprise would be safer from things like this. Start with unsafe then gradually convert into idiomatic Rust.

Your let's redo this in Rust made me wonder if generative AI will also be susceptible to software fads. One LLM writes a few blog posts extoling a new framework/lanaguge. Other agentics read these and get 'influenced'. Then they start clamoring for 'lets redo this in X!'. Can't wait to see it. /g

its bad enough when humans do it

Re: Did Claude increase bugs in rsync?

#314

Earlier quoted context omitted.

At my employer, if AI is not used, it shows up on your performance report and you’ll be told if you don’t start using it, you will be dismissed. I work at a medium sized successful YC-backed SaaS. So here, the attribution is meaningless - they look at your Bedrock and LLM API calls as well as Claude Code history.

Do you fellow ICs have access to those reports and can correlate commits from you to the prompts used to create them easily?

Not currently. Each IC's report is kept private unless they voluntarily share it, and IC's don't have visibility into other IC's Claude Code or Cursor logs. I think we're moving toward a model where it will be easier to correlate commits with chats, but timeline is not clear.

Re: Did Claude increase bugs in rsync?

#315
post #123

Earlier quoted context omitted.

I never care about AI usage disclosure, because I don't believe that human produced code is necessarily better than AI produced code, unless it's someone I personally know. People need to be responsible for code they commit and push anyways. This has never changed. Whether the code is written by hand, by their cat walking over keyboard, or by AI, is not my concern. A project's code quality can decline for all kinds o…

> People need to be responsible for code they commit and push anyways. Well the GPL (which rsync is licensed under) says: "This program comes with ABSOLUTELY NO WARRANTY" so actually nobody is responsible for anything.

Nobody is suing the maintainer for support here so this is completely irrelevant.

Re: Did Claude increase bugs in rsync?

#316

Earlier quoted context omitted.

Seems like someone could use Claude to port rsync to Rust and the whole enterprise would be safer from things like this. Start with unsafe then gradually convert into idiomatic Rust.

Your let's redo this in Rust made me wonder if generative AI will also be susceptible to software fads. One LLM writes a few blog posts extoling a new framework/lanaguge. Other agentics read these and get 'influenced'. Then they start clamoring for 'lets redo this in X!'. Can't wait to see it. /g

Prompt: automate writing commits to increase safety in these software projects so that my profile increases and I can snag a high-paying Rust job.

LLM: this commit changes whole codebase to Rust!

Re: Did Claude increase bugs in rsync?

#318

Earlier quoted context omitted.

Agree. From the article: > Here's my favorite part, though. Digging into the data, one of the first things that jumped out at me with blinding clarity was that the worst release, by far, in rsync history was entirely prior to the introduction of Claude ... And yet nobody noticed. Language really does suggest the article's author does have a dog in this fight and is cloaking opinion in fancy statistics jargon. "Blindi…

Also from the article: > "Claude clearly made things worse" &emdash; the main claim This article was clearly generated by AI, yet I found no mention/attribution of that by author. How likely is it than someone who vibe codes articles would also vibe code the underlying analysis and be eager to accept an outcome that is highly validating of that person’s workflow? I’d say very.

Are the numbers wrong? That's the only relevant thing here.

Also, humans do use em dashes, just FYI.

Re: Did Claude increase bugs in rsync?

#319

Earlier quoted context omitted.

No.

Yes.

You're not entitled to know what specific tools were used to produce something, generally speaking.

In the absence of such an entitlement, not volunteering to disclose the tools used is not fraud.

Re: Did Claude increase bugs in rsync?

#320

Earlier quoted context omitted.

[flagged]

The Fortune 10 company that I spent decades at and retired from just a couple years ago noticed this issue immediately and issued a blanket ban on the use of these tools for the company’s own code that to my knowledge has not been rescinded. (They also started developing their own coding-specific LLM, training solely on code they owned, around the same time.) You might consider that there is a very large incentive by…

They’re using Claude lmao
Post reply on HN