It sounds like the real problem, in this case, is communication. But the people writing are aware of it, otherwise, why on Earth are you going to share an extract of code in a Gist where you completely lose the context of the problem. And moreover, how're you starting a conversation by giving a question without contextualizing.
This sounds more like the kind of situation where a problem has an identified solution but the person thinks is better to create a new fancy product that was never necessary.
James to the team: Here is the PR. Let’s mob together what I did when no one else happened to be around (I don’t have full buy-in for 100% mobbing…but this is what I imagine)
Sounds like the problem is a unit of work is split between too many people, i.e. how the people in the example are using PRs, not PR (as a tool) itself.
It sounds like the real problem, in this case, is communication. But the people writing are aware of it, otherwise, why on Earth are you going to share an extract of code in a Gist where you completely lose the context of the problem. And moreover, how're you starting a conversation by giving a question without contextualizing.
This sounds more like the kind of situation where a problem has an identified solution but the person thinks is better to create a new fancy product that was never necessary.
@Sebastian what are your preffered solutions to addressing this problem? Can you share alternatives?
my PR (pull request - with self peer review)
James (3rd person): does this code look good?
James (3rd person): no you idiot
James (3rd person): correction incoming
James: lgtm! Approve & complete with squash merge
James to the team: Here is the PR. Let’s mob together what I did when no one else happened to be around (I don’t have full buy-in for 100% mobbing…but this is what I imagine)
Sounds like the problem is a unit of work is split between too many people, i.e. how the people in the example are using PRs, not PR (as a tool) itself.