A bogus study on code review
I don&#x27;t like code reviews, but it has a few benefits:<p>Pros:<p>1. Developers pay more attention to what they throw over the wall as a completed tasks because they <i>will</i> get grilled on it.<p>2. Reviewing other people&#x27;s code is good for learning a new system.<p>3. It keeps creating of methods that already exists to a minimum and boosts proper code reuse (of existing, difficult to find code).<p>Cons:<p>1. It takes a lot of time.<p>2. Petty arguments over style rather than technique. It can devolve into minutia &#x2F; trivia.<p>3. Once a developer &quot;gets the idea&quot; of how the organization wants coding done, it becomes more of a seemingly pointless routine.<p>I suggest code reviews for a developers first 3-6 months, or when working with new (to them) modules &#x2F; subsystems. After that, skip it (unless they are slow to conform).