Remix.run Logo
▲ cwel a day ago

> to fix problems that probably nobody will ever experience

Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I find that is most often the case. But there is definitely an increase in the "performance edge cases, or hypotheticals" framing, where I am equally befuddled/too tired.

▲Conscat a day ago | parent | next [-]

And personally I have never once opened a PR for any issue I didn't personally experience. Even when I used an LLM to assist, I've only worked on things I personally needed.

▲awakeasleep a day ago | parent | prev | next [-]

What makes you think a person is submitting the PR

▲cwel a day ago | parent [-]

Poor phrasing on my part, I should have said "the person involved in the PR", "the one behind the prompt".

▲kuriho a day ago | parent [-]

not the parent, but I received one PR adding a new feature to my and similiar projects at the same time. When I questioned the use case the PR sat around until it was closed months later. Hardly a real user.

▲j16sdiz a day ago | parent | next [-]

Before AI, I have submit PR band-aids bugs I personally experienced, but don't bother enough to fix it properly. When the maintainer ask about it, I move on and ignore it. I just don't care. Some maintainer found them useful, some don't.

I came from the "free software as in free puppy" camp. I would stop by to play with the puppy, but I won't feed it.

I guess if I do the same today, I might submit a better-than-band-aid fix from LLM. You would probably think I am not a real user.

▲kannanvijayan 16 hours ago | parent [-]

You're one of five hundred doing the same now for every nontrivial open source project. Your submission gets lost in the noise.

This sort of drive-by collaboration on open source is effectively dead in the water now. The technical talent to bang out a small fix for something is a commodity. The thing that's scarce is trust.

Someone merging a drive-by patch is going to have to spend a lot of time checking it carefully to make sure it's not a vulnerability injection in disguise. You simply can't ask for that kind of bandwidth from open source maintainers. They have lives.

The thing is that this was already sort of true before AI. Once tech effectively became the only job sector where salary wasn't garbage you had a ton of people whose only involvement in open source was as a resume booster. The tech version of high school extracurriculars to pad out your Ivy League application.

▲stackghost a day ago | parent | prev [-]

Sounds more like a real user than an LLM, which would have given you a 4-heading treatise where the third heading was some variation on “Why this matters”.

▲riedel a day ago | parent | prev | next [-]

Actually IMHO, we need better automatic build system integration with feature management. How cool would it be if the average user could vote with their feet if something is needed. Once there is enough adoption and no negative test reports consider merging it.

I guess also AI managed canary l releases could be an option IMHO that combine open PRs.

▲joshdata a day ago | parent [-]

> How cool would it be if the average user could vote with their feet if something is needed.

That's how things already work. Open source maintainers are balancing a vision with what people express they need.

▲joshdata a day ago | parent | prev | next [-]

> Have you considered that the person submitting the PR to fix said problem has themselves experienced it?

I have been asking PR authors lately how they came to submit the PR, and at least once and probably a few times it was that. I didn't make it up.

▲levkk a day ago | parent | prev | next [-]

That's not the case all the time anymore. It used to be. But it's not now.

So yeah, I've considered it and eliminated it for most PRs we used to get. Because no, a 2nd year student in university did not run into an obscure edge case in production that none of my 1M+ QPS users did.

▲zahlman a day ago | parent [-]

Sure, but maybe the reason you're getting PRs is because you have 1M+ "QPS users", whereas I can't even think off the top of my head what QPS stands for.

▲thinkmassive a day ago | parent [-]

Could be "users who handle 1 million queries per second"

▲zahlman 7 hours ago | parent [-]

Yes, I figured this out eventually.

The software world is far broader than web, never mind things that meaningfully make "queries". It's a little annoying seeing these kinds of assumptions taken for granted on HN. I would have expected proportionally more discussion of software that runs locally, including non-commercial things.

▲bmitch3020 21 hours ago | parent | prev | next [-]

> Have you considered that the person submitting the PR to fix said problem has themselves experienced it?

I've seen more and more PRs where when questioned about how the issue affected the submitter, they replied that they weren't even a user of the project. There are way too many drive-by AI submitted PRs now, where it's clear the submitter is farming for reputation.

It's also happening in security vulnerability reports. I'll see reports that start with "assume your package repository is malicious" and report a blind http redirect where if lots of those requests happened to be queued up you may be able to port scan a private network. And I'm like, my dude, a malicious package repository is by definition a remote code execution on every client, stop wasting my time.

Until GitHub introduces a way to track how many issues, PRs, and security reports the user submitted that were rejected as invalid, and publicly labels users wasting maintainer time, this problem is going to keep getting worse. Maintainers are going to burn out or delegate maintenance to an AI until quality degrades. Neither of those are good for the open source ecosystem.

▲matkoniecz a day ago | parent | prev [-]

> Have you considered that the person submitting the PR to fix said problem has themselves experienced it?

I had multiple PRs for entirely hallucinated problems.

Or where no human ever looked at project or PR and were just attacking open source projects with spam PRs pretending to be contributions. Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

▲shagie a day ago | parent [-]

> Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

I believe a fair bit of this is an attempt to gain numbers where quantifiable numbers are advertised on otherwise indistinguishable resumes (with the corresponding belief that those numbers make differences in filtering or hiring decisions).

I base that on having seen people in the days of old put their Stack Overflow reputation on resumes thinking that having a rep of 4321 will be more likely hired than someone with a rep of 1234.

Having "210 accepted PRs on GitHub" (they believe) would appear to make them a more productive / less risky hire than someone who hasn't done any.

---

This is really a case of indistinguishable resumes where nearly everyone in the pool went to the same college, same internships, same capstone project, and maybe the same first year or two of professional experience.

▲JDups a day ago | parent [-]

There are job applications that list having a certain amount of contributions to github projects as a requirement. Encourages useless spam. Also funny the implication that only projects on github have any worth.

▲shagie a day ago | parent [-]

That wouldn't surprise me in the slightest. I see it with applicants for a position that doesn't have GitHub contributions listed as either a requirement or a nice to have.

I could see it as a "proof of familiarity with CI and expectations for a PR", though for applicants that are spamming the process with poor PRs (and people posting poor Q&A on Stack Overflow back in the day), this often hurts them more than it helps as its a demonstration of what they are going to be doing if they are hired (I've already got too many poor quality PRs to review, your PRs would not reduce the amount of time that the reviewer would need to spend).