Update wording to reflect teams' shared responsibility #161
Conversation
This file contains 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
In a no-blame culture, all the work we produce is a shared responsibility. This means if a change causes an incident, it isn't the fault of the engineer that made the change. This cuts both ways though, if delivering software is a shared responsibility then this means reviewers aren't completely absolved. I believe this change better reflects the reality of how teams work here today. With the rise of AI-assistants, we will need to instill a renewed focus on code review and I believe that even more than now, a shared responsibility model for teams will be essential. This change serves as a trigger for checking that my sense of how this works is shared, ahead of rolling out guidelines for the use of AI assisted programming.
NovemberTang
approved these changes
Mar 14, 2024
bryophyta
approved these changes
Mar 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is being recommended?
In a no-blame culture, all the work we produce is a shared responsibility. This means if a change causes an incident, it isn't the fault of the engineer that made the change. This cuts both ways though, if delivering software is a shared responsibility then this means reviewers aren't completely absolved.
What's the context?
I believe this change better reflects the reality of how teams work here today. With the rise of AI-assistants, we will need to instill a renewed focus on code review and I believe that even more than now, a shared responsibility model for teams will be essential.
This change serves as a trigger for checking that my sense of how this works is shared, ahead of rolling out guidelines for the use of AI assisted programming.