What do you mean, 'work'? There are a few characteristics that code review has- - it brings more eyeballs on the code - it brings to light strange practices

What do you mean, 'work'? There are a few characteristics that code review has- - it brings more eyeballs on the code - it brings to light strange practices - the author must explain himself to others, and a Teddy Bear effect can transpire - it standardizes practices and approaches - knowledge is shared - it slows deployment - it promotes egoless coding (and big egos can't take it) > I've heard it argued that quality scales proportionally to the number of reviewers a patch must go through before being accepted. Each reviewer brings his own practices and understanding to the table, so the more reviewers, the more experience in the review. I'd reckon that it scales logarithmically though... after enough reviewers, the marginal value is slight. --- That's not research, it's just my personal experience.