 &gt; Humans cannot write correct code, and the way to keep high code quality is to maximise our ability to fix the errors that result from having humans involved.<p>This kind of breeds a dilemma: If humans don&#x27;t know how to write correct code, why are we trusting them to verify code correctness? :)<p>No matter how many times I run jslint, I always get the same result, however if I would show the same code to 20 programmers, I&#x27;m pretty sure I would get a lot of different results.<p>&gt; If your team members are engaging in passive-aggressive abuse then you should find new ones, not try to do your job without interacting with them.<p>If your friend looks at your code, (s)he&#x27;ll find a lot less issues than your rival. We software engineers are not emotionless objective beings.<p>My issue is that I have seen few issues that could have been caught in time by code reviews with the cost of the code review being less than the cost of just fixing the problem. Code reviewing every change is continuos effort, that might cost more than having a few quirks and fixing it.<p>I do understand some projects do require every kind of verification process you can throw at it, like software that controls nuclear power plants, however not everyone is building that kind of software.