admin: Some revisions to the AI Coding policy - #5446
Open
lgritz wants to merge 1 commit into
Open
Conversation
Trim the section about disclosure to the essentials. The previous overly-verbose part asking for detailed explanation was a sign of my inexperience with the tools at the time I wrote it. I've used them extensively for many months now, and I see that it's often a complex, protracted, circuitous interaction that defies easy summary. Tweak the language to slightly loosen the conditions for when to disclose. We care about disclosure when the tools are materially used for drafting code, designing the approach, finding the bug, or suggesting the specific fix. We really don't care about mechanical changes like moving code around or certain minor refactoring that's just an extension of what IDE, search-and-replace, and compiler warnings with specific change hints have been doing for us for a long time. Add a couple more references for some new things I've seen lately that inform my thinking on how to use the tools wisely. Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trim the section about disclosure to the essentials. The previous overly-verbose part asking for detailed explanation was a sign of my inexperience with the tools at the time I wrote it. I've used them extensively for many months now, and I see that it's often a complex, protracted, circuitous interaction that defies easy summary.
Tweak the language to slightly loosen the conditions for when to disclose. We care about disclosure when the tools are materially used for drafting code, designing the approach, finding the bug, or suggesting the specific fix. We really don't care about mechanical changes like moving code around or certain minor refactoring that's just an extension of what IDE, search-and-replace, and compiler warnings with specific change hints have been doing for us for a long time.
Add a couple more references for some new things I've seen lately that inform my thinking on how to use the tools wisely.