Hacker News Reader

Thanks for the detailed feedback. I agree with a lot of your points, but I don't think adding QA people addresses the same need as peer code review. QA can find bugs in the current code whereas code review is more about finding issues that may lead to bugs further down the road. Even when there are defects in the current code, they may be edge cases that QA is unlikely to unearth but that will come out in a thorough code review.

View on HN

None of the techniques we have are exact drop in replacements of one another. But they are all techniques that improve quality. I've seen a good QA person in the right environment be 100x as valuable as all the unit tests and code review combined.

Thats why the answer is really heavily dependent on your team and your project. The key though is considering what you aren't doing because you are focusing so heavily on code review.

Reply on news.ycombinator.com