How to do a code review
&gt; Some hardward manufacturers only ship new hardware once a year.<p>A line snuck in through their code review.<p>One big issue that I&#x27;m not really seeing discussed is that in many cases code reviews end up being very subjective.  &quot;hard to maintain&quot;, &quot;not readable&quot;, &quot;brittle&quot;, &quot;needs more tests&quot; are all super subjective.  There is no magic tool that can tell you the future maintenance costs (vs. the current costs), whether some area is more likely to see issues, etc.  A lot of this is a matter of judgement.  One old recommendation I recall is to limit the scope of code reviews to finding bugs.  If there is a bug that&#x27;s pretty objective, the code does not work.