> Over the shoulder is often the developer explaining their decisions in the code, instead of the reviewer trying to reverse-engineer it, independently. It's just faster and has less resistance -- not necessarily better.
Ouch, this is a great point. So for code that has to live for a long-ish time over-the-shoulder review is definitely inferior.
I have setup review process in a company I work in, and one of the rules is "the best way to answer the reviewer's comment is to change the code or add a comment".
Ouch, this is a great point. So for code that has to live for a long-ish time over-the-shoulder review is definitely inferior.
I have setup review process in a company I work in, and one of the rules is "the best way to answer the reviewer's comment is to change the code or add a comment".