←back to thread

728 points freetonik | 2 comments | | HN request time: 0.492s | source
Show context
Waterluvian ◴[] No.44976790[source]
I’m not a big AI fan but I do see it as just another tool in your toolbox. I wouldn’t really care how someone got to the end result that is a PR.

But I also think that if a maintainer asks you to jump before submitting a PR, you politely ask, “how high?”

replies(16): >>44976860 #>>44976869 #>>44976945 #>>44977015 #>>44977025 #>>44977121 #>>44977142 #>>44977241 #>>44977503 #>>44978050 #>>44978116 #>>44978159 #>>44978240 #>>44978311 #>>44978533 #>>44979437 #
armchairhacker ◴[] No.44978050[source]
Agreed. As someone who uses AI (completion and Claude Code), I'll disclose whenever asked. But I disagree that it's "common courtesy" when not explicitly asked; since many people (including myself) don't mind and probably assume some AI, and it adds distraction (another useless small indicator; vaguely like dependabot, in that it steals my attention but ultimately I don't care).
replies(5): >>44978496 #>>44978872 #>>44979119 #>>44979194 #>>44981592 #
eschaton ◴[] No.44978496[source]
It’s not just common courtesy to disclose, it’s outright fraud not to disclose.
replies(1): >>44982414 #
Aeolun ◴[] No.44982414[source]
That's nonsense. It's like feeling you need to disclose that your IDE has autocomplete. Nobody discloses that, since it's ridiculous. You only disclose that you used Claude Code if you are not certain of the result (e.g. you think it is correct, but the maintainer might be a better judge).

If it's exactly the same as what you'd have written manually, and you are confident it works, then what's the point of disclosure?

replies(1): >>44987971 #
1. eschaton ◴[] No.44987971[source]
It’s completely different from an IDE’s autocomplete because autocomplete in an IDE is only helping you type identifiers that already exist in your codebase or in any SDKs you’re using.

An LLM is regurgitating things from outside that space, where you have no idea of the provenance of what it’s putting into your code.

It doesn’t just matter that the code you’re contributing to a project is correct, it matters quite a lot if it’s actually something you’re allowed to contribute.

- You can’t contribute code that your employer owns to a project if they don’t want you to. - You can’t contribute code under a license that the project doesn’t want you to use. - And you can’t contribute code written by someone else and claim it’s your intellectual property without some sort of contract in place to grant that.

If you use an LLM to generate code that you’re contributing, you have both of the latter two problems. And all of those apply *even if* the code you’re contributing is identical to what you’d have written by hand off the top of your head.

When you contribute to a project, you’re not just sending that project a set of bits, you’re making attestations about how those bits were created.

Why does this seem so difficult for some supposed tech professionals to understand? The entire industry is intellectual property, and this is basic “IP 101” stuff.

replies(1): >>44994040 #
2. Aeolun ◴[] No.44994040[source]
> Why does this seem so difficult for some supposed tech professionals to understand?

Maybe because 99% of people that complain about this complain about problems that never occur in 99% of the cases they cite. My employer isn’t going to give a shit that code that I’ve written for their internal CRUD app gets more or less directly copied into my own. There’s only one way to do that, it was already in my head before I wrote it for them, and it’ll still be in after. As long as I’m not directly competing with their interests, what the hell do they care.

> When you contribute to a project, you’re not just sending that project a set of bits, you’re making attestations about how those bits were created.

You are really not. You are only doing that if the project requires some attestation of provenance. I can tell you that none of mine do.