I will never understand why we looked at modern programming, saw that there is a good bit, which is programming, and a bad bit, which is code review… and decided to automate the good bit at the expense of having to do a lot more of the bad bit.

@samir Respectfully I think that's ... maybe the inverse?

We automated the bad bit, which is "generating the text", in a way that obviates the important part, of creating a community of comprehension around the problem we're solving.

@mhoye I don’t think you can separate these two things.

And I prefer my sharing through pair or ensemble programming, not asynchronous reading, which always misses the important part (e.g. “why are we doing this, anyway?”)