Hacker News Reader

All those practices are good (tdd, code review, etc) if people know what they're doing

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

A pissing match of who can find the most errors in other people's code is probably a good thing :P It's when it starts being about personal aesthetic preferences without any consequences in terms of code readability/quality that I think it starts to be annoying.

Yes, there's usually a finite amount of errors in a given code.

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)

Reply on news.ycombinator.com