Comments by "Michael Stover" (@michaelrstover) on "Why Pull Requests Are A BAD IDEA" video.

@obfuscator2 I agree with your assessment of the value of flow. Usually flow means your internal editor is off and you're writing code with a filter. Bad. However, I still can't pair programming because when I'm thinking with another, I'm no longer me. Instead, I'm spending more time going at my partners speed, or thinking about things the way they think about things. By myself, I'm usually very very different in my approaches to problems. One example, I'm highly experimental. But I won't drag others into my crazy experiments, and so that whole part of me would just vanish.
10
@alrightsquinky7798 We didn't say anything about not being team players or writing code others can't understand. You've misinterpreted our words.
7
My solution would be a once a day code review meeting done on a single PR for the team. Ie, the team works on a sprint "trunk" during the sprint. Every developer pushes changes to it as they work. Once a day, the team gathers (perhaps in place of scrum standup) and goes over the committed changes since the day before, resolves issues and merges the PR. Obviously, your teams would have to be small (ie, no more than 5 devs).
1