News for hackers. Stuff that matters.
Re:Code Review Best Practices by dewiz on Sunday May 10, 2015 @03:42AM (#9519217)
Try with design sessions upfront, i.e. discuss how the problem should be solved in terms of patterns and architecture. Once that is agreed, with 2-3 people, then the code review becomes simply a matter of style and there you can only invite for consistency with the rest of the code base. Often the problem is in the tools, face to face conversations, pair programming, human interaction help with that. You can also have your colleague help with a task of yours and show that you appreciate his input.
Re:Code Review Best Practices by maguirre on Sunday May 10, 2015 @11:32PM (#9522549)
+1 This is something I've been meaning to introduce. We're slowly moving from the idea of hacking away and making things work to the idea of making production ready code and this mentality is not getting through to everyone