←back to thread

728 points freetonik | 2 comments | | HN request time: 0s | source
Show context
andruby ◴[] No.44977657[source]
> I try to assist inexperienced contributors and coach them to the finish line, because getting a PR accepted is an achievement to be proud of

I really appreciate this point from mitchellh. Giving thoughtful constructive feedback to help a junior developer improve is a gift. Yet it would be a waste of time if the PR submitter is just going to pass it to an AI without learning from it.

replies(1): >>44979267 #
ants_everywhere ◴[] No.44979267[source]
Junior developers are entering a workforce where they will never not be using AI
replies(5): >>44979792 #>>44980077 #>>44981765 #>>44982323 #>>44984099 #
eru ◴[] No.44979792[source]
I don't think using AI at all is forbidden, he just doesn't want AI to do the whole PR?
replies(1): >>44979840 #
ants_everywhere ◴[] No.44979840{3}[source]
The requirement is explicitly

> If you are using *any kind of AI assistance* to contribute to Ghostty, it must be disclosed in the pull request.

This is sufficiently confusing that someone is asking if this applies to tab completion. They commit actually says

> trivial tab-completion doesn't need to be disclosed, so long as it is limited to single keywords or short phrases.

So if you take this literally you're going to be disclosing every yasnippet expansion that completes boilerplate.

The policy as written isn't sensible and I don't think it's entirely coming from a sensible place.

Junior developers need to learn how to code with AI because that's what coding is now. Not that he has to help them. But it does read a bit weird to toot your horn about how important it is to be helpful until it comes to helping people understand how to navigate the current environment then it's not worth your time.

replies(2): >>44980135 #>>44984098 #
1. 0x6c6f6c ◴[] No.44980135{4}[source]
Disclosing doesn't mean it will be declined, it's just a signal for reviewers.
replies(1): >>44985518 #
2. rerdavies ◴[] No.44985518[source]
The question is going to be: is it a USEFUL signal. I suspect not. And frankly, to be honest, as a senior developer who uses AI assistants routinely, I would consider it a serious disincentive to actually submit a PR in the first place to a repository that has such a policy. Submitting a good PR is hard work. Often an order of magnitude more work than the fix itself. If I think that a repository is going to not accept my PR just because I use a coding assistant, I'm going to be much less inclined to submit a PR at all.