Hacker News new | ask | show | jobs
by awesome_dude 18 days ago
When a paper is submitted to a reputable publication references are demanded.

You have to let people know where your ideas are supported, or even come from.

To do anything else is plagiarism.

AI isn't a co-contributer - but it should be referenced - just like a link to a Stack Overflow comment when that's the source of code.

Having AI referenced in the commit is (IMO) best practice - but only co-contributer attributes are available (for now)
2 comments
dalemhurley 18 days ago
Disagree, I never attributed Laravel Artisan or all the other code generators.

Right now you could run Laravel new app (replace with any new framework) and Claude/Cursor/Codex git commit will claim to of created the code.

link
awesome_dude 17 days ago
To be fair I've never used Laravel - but I do have a memory of code generators/scaffolders inserting files that made clear they were responsible for work

/*

* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

* Do not edit the class manually.

*/

link
sdevonoes 18 days ago
Do I need to write “coauthored by protoc” when pushing grpc changes? “Coauthored by gofmt” when formatting? “Coauthored by React when using npx create-next-app”?

No. So, same goes for ai

link
awesome_dude 17 days ago
Have a look at the top of the files generated by protoc bud ;)

It's not in the git commit, it's in the files themselves - is that what you want for AI instead?

link