1
I'm planning on doing my own research into what makes for a productive code review (my initial research has turned up 'Peer Reviews in Software: A Practical Guide'), but also wanted to ask the community.
(For clarification: - this is not an 'architectural review, per-se; rather, a more narrow scope into code after the architecture has been defined, vetted and approved - this is also in addition to the user of profilers and automated code checking tools).
Thank you in advance to those who take time to respond!