News for hackers. Stuff that matters.
Re:We don’t have time for code reviews by benihana on Wednesday October 23, 2013 @09:51AM (#6598688)
Code reviews are about psychology. When you know your teammates are going to be reviewing your code, you write it differently than you do when you know no one but you will ever look at it.

Static analysis and regression tests are tools to make sure the code isn't broken.

Re:We don’t have time for code reviews by masklinn on Wednesday October 23, 2013 @09:55AM (#6598729)
> Code reviews are about psychology.

Code reviews are also about distance from the code. When it's your production it's easy to miss the forest for the trees. That's why books are generally better when beta readers or reviewers are involved.

Code reviews are also about spreading knowledge (about the subsystems and about choices made in implementation and the reason for them) and increasing the code's bus factor.