Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the gist and the "virality" of this policy is:

1) we accept good quality LLM code

2) we DO NOT accept LLM generated human interaction, including PR explanation

3) your PR must explain well enough the change in the description

Which summed together are far more than "no shitty code". It's rather no shitty code that YOU understand



> 1) we accept good quality LLM code

there is no such thing as LLM code. code is code, the same standards have always applied no matter who or what wrote it. if you paid an indian guy to type out the PR for you 10 years ago, but it was submitted under your name, its still your responsibility.


I don't agree at all. There's a huge difference between "someone wrote this code and at least understands the intention and the problem it's trying to solve" and "the chat bot just generated this code, nobody understands what the intention is". I'm comfortable having a conversation with a human about code they wrote. It's pointless to have a conversation with a human about code they didn't write and don't understand.

The quality of "does the submitter understand the code" is not reflected in the text of the diff itself, yet is extremely important for good contributions.


> It's pointless to have a conversation with a human about code they didn't write and don't understand.

this was a problem before LLMs


Scale can be transformational: getting shot was always bad but when guns lowered the skill requirement and increased lethality wars became even more deadly. LLMs greatly increase the pool of potential scammers and the cost of detecting them.


It was, and those PRs should be banned too...


LLM code and code written by a human are not fungible.

When it comes to IP, LLM output is not copyrightable unless the output is significantly modified by a human with their own creativity after it is generated.


Errata: I obviously meant "no shitty (or good) code that YOU DO NOT understand"




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: