Post #1966170

@curiouserrandy Yeah, I am also thinking along similar lines. The more I think about it recently, code review has ended up in an awkward place: - Try to do optional code review, it just never happens - Eventually, make it mandatory and pre-commit to ensure it happens - Ooops, now it's not just a second set of eyes, it's a layer of review process to make progress Pair programming I think neatly side-steps this doom loop, which in nice. But it has its own challenge due to its synchronous nature: timezones. This makes it incredibly difficult to insist on, especially in environments like open source projects. What I want is an async code review process that _feels_ more like pair programming rather than a layer of review, and so doesn't explode to the 10x cost. But not sure how to achieve that (yet).