i agree with the author in that i personally don't like code reviews much as well, though i agree they are valuable. to be more specific though, i don't like "

i agree with the author in that i personally don't like code reviews much as well, though i agree they are valuable. to be more specific though, i don't like "remote" or "detached" code reviews much; "over the shoulder" code reviews are a completely different thing. as you can actively communicate with the author or the reviewer, it tends to reduce the bike shedding a lot and the value of positive feedback increases. i guess, ultimately, it depends on the team; if you're operating well together, classic code reviews might work as well. if the team is new or the members have varying styles or levels of exerience, over-the-shoulder reviews tend to pay off significantly.