Live data from Hacker News

We will ban you and ridicule you in public if you waste our time on crap reports

curl.se

421–430 of 653 posts

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#421

Earlier quoted context omitted.

>Indian students Resume glorification and LinkedIn / GitHub profile attention do that. I am seeing a lot of people coming up with perceived knowledge that's just LLM echo chambers. Code they contribute comes straight out of LLMs. This is generally fine as long as they know what it does. But when you ask them to make some changes, some are as lost as ever. Torvalds was right, code maintenance is going to be a headache…

> Torvalds was right, code maintenance is going to be a headache thanks to LLMs. I know someone in a senior engineering position at Epic who does nothing but clean up PR's from their off-shored Ukrainian sweat shop coders handing in AI slop because all they need to do is close a ticket to get paid. They wind up rewriting half or more of it. Epic doesn't seem to care so long as this "solution" works and saves them mon…

As if I needed another reason not to hire people coming from Epic.

For a company as financially focused as Epic it's surprising to me they'll pay the offshored devs for simply submitting code even if it doesn't work and needs to be rewritten.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#422

Earlier quoted context omitted.

I've seen this - it's tiring even at low volume. Goes something like: Someone creates a garbage issue. Someone else asks to be assigned. Someone from the project may say "we don't assign issues" (this step has zero effect over later steps). Someone else submits a PR. Maybe someone else will submit another PR. Maintainers then agonise how they can close issues and PR(s) without being rude or discouraging to genuine ef…

GitHub PM here working on how we can make this problem feel better for maintainers. Really appreciate how tiring this can be, especially when even low volume is sustained for many months. Would love your thoughts on some of the things we're thinking about: - Would it help to disable all PRs? All non-contributor PRs? - Would a "close as admin" button help address the issue of not wanting to be rude or discouraging? -…

As someone on the other side of the PR, the current situation makes things awkward for me, too. Occasionally, I'll make an actual fix to scratch some particular itch I have with the software, and I'm hesitant to even open a PR, because it's just going to 1. pile yet another PR onto the maintainer, and 2. might get dismissed out of hand because it's mistaken for AI slop or other low-effort spam that these attackers are doing. So, I usually just fork, make the change in my own repo, and leave it at that.

Disabling PRs or limiting PRs to "contributors" would be a signal to me that I should just keep doing that and not contribute back to the main repo.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#423
post #201

Earlier quoted context omitted.

Could you expand on the other problems with Europe other than hiring and firing laws?

Senior/staff type engineers are not a union position so great people refuse promotions and responsibility because they don't want to leave the union. Thus they won't mentor juniors, and other things that you need great engineers for. (At least that is how the union people I work with in Europe are, there are other unions with different rules) There is probably more.

Never heard of that, nor of a union in tech. What part of Europe?

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#424

Earlier quoted context omitted.

> Indian students Is this cultural? I ran a small business some years ago (later failed) and was paying for contract work to various people. At the I perceived the pattern that Indian contractors would never ever ask for clarifications, would never say they didn't know something, would never say they didn't understand something, etc. Instead they just ran with whatever they happened to have in their mind, until I cal…

Definitely not. Anyone growing up immersed in face-saving, high pressure, competition and possibly self-help influencers telling them how to achieve will exhibit these sorts of behaviors. Doesn't matter if you're white or black.

> Doesn't matter if you're white or black.

Disingenuous. Other groups can and do create different cultures that are more tolerant of asking for help, clarification and feedback.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#425
post #421

Earlier quoted context omitted.

> Torvalds was right, code maintenance is going to be a headache thanks to LLMs. I know someone in a senior engineering position at Epic who does nothing but clean up PR's from their off-shored Ukrainian sweat shop coders handing in AI slop because all they need to do is close a ticket to get paid. They wind up rewriting half or more of it. Epic doesn't seem to care so long as this "solution" works and saves them mon…

As if I needed another reason not to hire people coming from Epic. For a company as financially focused as Epic it's surprising to me they'll pay the offshored devs for simply submitting code even if it doesn't work and needs to be rewritten.

> As if I needed another reason not to hire people coming from Epic.

I don't understand, are you threatening to avoid hiring talented people or just their brain dead management?

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#426

Earlier quoted context omitted.

I contribute regularly to some major open source projects and it’s happening here too. So many issues that aren’t issues. Constant “fixing” of documentation that doesn’t need to be fixed. Bug reports that aren’t bugs, followed by a bad PR “fixing” the “bug.” Or YOLOing an LLM PR to change major behavior that users are relying on. And I click and the authors are always brand new, with only vibe coded or examples proje…

GitHub PM here. From what we've seen, you're right about the motivation; I've also seen plenty of job ads where "significant contribution to open source" is something that's called out explicitly as a valid substitute for professional experience in the area. While that's always well-intentioned and creates many benefits for the OSS community, the flip side is that it can also lead to the kind of problems you're seein…

I get a lot of unsolicited PRs on my projects that I don't actually want

Turning off PRs would be a good option for several of my repos

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#428

Earlier quoted context omitted.

I contribute regularly to some major open source projects and it’s happening here too. So many issues that aren’t issues. Constant “fixing” of documentation that doesn’t need to be fixed. Bug reports that aren’t bugs, followed by a bad PR “fixing” the “bug.” Or YOLOing an LLM PR to change major behavior that users are relying on. And I click and the authors are always brand new, with only vibe coded or examples proje…

GitHub PM here. From what we've seen, you're right about the motivation; I've also seen plenty of job ads where "significant contribution to open source" is something that's called out explicitly as a valid substitute for professional experience in the area. While that's always well-intentioned and creates many benefits for the OSS community, the flip side is that it can also lead to the kind of problems you're seein…

It would help if PRs from newly-created or private accounts could stand out. And perhaps PRs from accounts that spam multiple PRs with dozes or hundreds of commits, would have some kind of a warning that only people with write access to repos can see. In fact perhaps GitHub could throttle those accounts from creating that many PRs in the first place.

Another suggestion would be trying to figure out if a PR was vibe-coded and marking them as such. Same as image-based social media tries to do.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#429
post #211

Long time ago Sourceforge and then GitHub promoted into the current default the model of open source distribution which is not sustainable and I doubt it is something that the founding fathers of Free Software/Open Source had in mind. Open source licenses are about freedom of using and modifying software. The movement grew out of frustration that commercial software cannot be freely improved and fixed by the user to…

> I doubt it is something that the founding fathers of Free Software/Open Source had in mind. Free Software sure, that wasn't the point. Open Source, that was exactly the point. Eric S Raymond, one of the original promoters of the concept of Open Source coined Linus' Law: Given enough eyeballs, all bugs are shallow Which definitely points in the direction of receiving bug reports and patches from users of the applica…

ESR is also from a time where spamming countless reports/junk code wasn't really a concept.

They did have things like trolls and zealots that thought "Their one idea" was a gift from god and the maintainers were idiots for not adding it to the application. And eventually those people may have been banned from mailing lists. But in general the people posting code were typically well known and had some interest in fixing the application for some useful purpose.

Simply put, no idealism stands the test of time without change. Nature shows us that everything must evolve or it goes extinct. How 'free software' evolves is now up for debate.

Re: We will ban you and ridicule you in public if you waste our time on crap reports

#430

Earlier quoted context omitted.

Great example. I work in a radiology practice and greet patients regularly. 99% of them say the are good/great etc. It’s quite a striking response when they are limping, bandaged and on crutches.

Is that just a reflex response though? I would expect people to be more deliberate in their interactions with medical professionals, but I can easily imagine hearing “How are you?” and my brain goes on autopilot.

The greeting is generally in the waiting room. I’d do exactly the same if I was them.
Post reply on HN