that's expected, really. code reviews are not substitute for a design review; there is a limited amount of mental power that a reviewer can expend. the purpos

that's expected, really. code reviews are not substitute for a design review; there is a limited amount of mental power that a reviewer can expend. the purpose of code reviews, in my opinion, is to a) catch any obvious problems b) propagate a vague understanding of the change among the team members anything more requires much more work on the part of your team mates and probably needs to be explicitly scheduled (design review, implementation review), possibly in a different format, for example 1:1 conversation or during a lunch.