Hacker News Reader

Comment by crossroadsguy | Hacker News Reader

How does all this AI generated code blocking gappen? Does a human decide that or an AI is tasked with sequencing that PR's DNA to ascertain its possible inhuman origins?

What if someone generates code with AI and then goes into the IDE and then bathes it, dresses it (including adding comments) etc, in a way a human would? What then? No, here I am not exploring a way to fool the code DNA checking, but rather trying to find out what the real problem is with the AI generated code? (Other than license issues, too many PRs etc)

View on HN

The "blocking" happens on the side of the AI users. You like using AI. You are aware of this policy.

Will you submit an AI-generated pull request to OpenJDK? No? Voilà, you have successfully self-enforced the OpenJDK policy.

Or do you go to the trouble of finding an interesting issue to work on, get your agent to code it up, manually polish it to make it less AI-looking in case there are doubts, and then submit it? Yes? No. Why would you? To prove some kind of point, to yourself, that you can never disclose publicly? Most people have better things to do. Voilà, the policy is, again, self-enforced. Enjoy your day at the beach instead of trying to trick a project that is politely asking you not to trick it!

They're just so information-dense and sprawl in scope.

Too many PRs wouldn't be a problem if they were easily digestible: But they often include these giant refactors with confusing changes that aren't elaborated.

The real underlying problem is with authors who do not understand the code they submit. If you cannot defend the PR, you shouldn't be submitting it.

The FAQ addresses these questions: https://openjdk.org/legal/ai

There is a more helpful way to reply, that includes this text.

I believe in linking over copy & paste, in particular when I want neither to quote the full FAQ nor editorialize by selective quoting. By reading the FAQ, people can form their own opinion on it.

> Other clues include highly structured comments with multiple headings, unnecessary comments in code, gratuitously defensive programming, and the use of emoji characters.... In general, if something in a pull request seems uncannily cheerful or meticulous then you could be looking at AI-generated content.

So, get rid of formatting, throw in an innocent grammatical mistake, intentionally omit an obscure corner case while alluding to an existential crisis for taking compromises and you're good to go!

They look at your code, and if they think it's AI, they say no.

Reply on news.ycombinator.com