No surprise that Kent Beck's article "Thinking about Code Review" has an excessively good value:words ratio. His point about incentives of pull-requests is spot-on, and I really like this quadrant. tidyfirst.substack.com/p/thi…
| | blocking | non | | sync | pairing | ? | | async | P.R. | review | | | | |

ALT | | blocking | non | | sync | pairing | ? | | async | P.R. | review | | | | |

Apr 6, 2023 · 6:41 PM UTC

12
88
440
74,291
Sort replies: Relevant Recent Liked
Replying to @martinfowler
One way to fill in the top row is: enforced pairing | optional pairing.
2
10
6,897
Replying to @martinfowler
Love it. "Rowing. We’re all in the same boat, so it doesn’t matter how fast one person can row, it matters how fast we can row together."
1
9
1,786
Replying to @martinfowler
"Review", I assume, can refer to post-commit reviews. I have done that and it works just fine (remember @javisan81 ?). The value of PRs to prevent mistakes is way lower than most people thinks.
3
3
1,708
Replying to @martinfowler
"Think. Experiment. Share." Thanks for sharing Martin
2
554
Replying to @martinfowler
The question mark could be an AI based IDE tool that comments /highlights problems, but unlike a human pair, can be easier ignored.
496
Replying to @martinfowler
@apostolis09
1
826
Replying to @martinfowler
The clarity this sketch provides is astonishing🙌.
33
Replying to @martinfowler
Synchronous nonblocking are all code analyzers, syntax checkers, some tests and LLMs like chatGPT.
428
Replying to @martinfowler
Sync + Now = mobbing?
556
Replying to @martinfowler
I love this and going to find the balance in my team! How does this conform with being familiar with changes done by other team members?
1,184
Replying to @martinfowler
"Pick the style of review that matches your context. Invent a new one if necessary. Don’t just copy the open source pull request model just cause. Think. Experiment. Share." ❤️
999
Load more