re: Code Reviews Are Awesome, Here Are 7 Reasons Why VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Hi, nice article. Let me try some another approach. I saw a lot of benefits really similar when we are pairing in all development about the feature...
 

And, answer your question in my current project we are pairing and doing a code review. As we have a distributed/remote team with different timezones this way have been extremely helpful for us. As the code is a legacy usually we can have someone that already touched in that code looking on this and bringing up some new context about some decisions made.
In a mature team my feeling is that the code review is almost optional since we are doing the cards pairing and with pairing rotations.

 

Regarding the mature team, I personally think it is still worth reviewing (or pairing). It will still help to find bugs and problems and will spread the knowledge about new features.
If you feel pairing helps you to achieve all that, perfect!:)

Do you pair 100% of time? Can you tell me a bit about the process when you pair?

code of conduct - report abuse