Found that paper about code reviews, it is mentioned in this blog post: http://kev.inburke.com/kevin/the-best-ways-to-find-bugs-in-y...
And here's the link to the paper itself: http://kev.inburke.com/docs/basili_testing.pdf
Otherwise:
Sometimes code review will turn into a pissing match of who can find the most errors in other people's code
TDD will turn into a quest for a higher "coverage number" regardless of the actual testing quality
But it's mostly about, as you said, personal preferences or 'philosophies' regardless of the actual results of the code.
So you waste a lot of time because someone thinks the way you did it is not 'OO enough' or 'should be organized better' even if it is working (I'm not talking about code that's messy)