# of code reviews is a metric I see on a lot of performance evaluations for TLs and senior engineers. As is some feedback from their team about the quality of c

# of code reviews is a metric I see on a lot of performance evaluations for TLs and senior engineers. As is some feedback from their team about the quality of code reviews. Shifting some coding norm through code reviews such that a better practice becomes the default is seen as a substantial form of impact. Code reviews also have some more intangible benefits. If I am reviewing a substantial portion of the code in my codebase then I am less likely to be completely unaware of some module or design when there is a problem and we are digging in to debug.