Unpopular opinion: code review is a big loss of time if done systemically. Could be you some times but for me. It's hard to get a good opinion on others code with just a quick read. Most of the time, the feedbacks are just on the form not on the functionality. If the reviewer is good at coding, the feedback will be good but the time should be better used to produce something else. If the reviewer is less good, the feedback will be useless mist of a the time.
And the reviewed loss some of responsibility on the code he produce because "it'll be reviewed". Each one has his way to code. For me, the final project is the main target, not the way we are making it. Most of the time, the code produced just work, because programmer did their job as best as they can and just work fine. Need nothing more. For the rest, the debug phase will do the job to get a perfect final product.