I really like continuous integration&#x2F;automated tests&#x2F;code coverage dashboards&#x2F;automated lint checkers, etc. The more decisions you can cleanly take away, the easier it is to work in a codebase. I agree with you there.<p>Once you have all that, the purpose of a code review changes a bit, but it is still really useful. Maybe you don&#x27;t need locking, or maybe you should rewrite the base class, or maybe there is some other part of the code base that should be folded in, or maybe a better interface&#x2F;algorithm. Stuff like that is hard for a computer to detect for you, at least for the next decade or two :).<p>The really big thing I push in code reviews is defensive programming. I want to make sure someone in a 2 years, who isn&#x27;t familiar with the code, will not screw up the  codebase after the original authors may have moved on to other things.