I was having a discussion with a fellow developer and we were talking about QA practices. I was thinking that code review would be a QA practice because you're not making anything, but rather are inspecting it. He said it's part of the development process because it deals directly with the code, not just functionality or abstract concepts.
I can see his point of view, and now it has me thinking: code reviews are PEER reviews - they should be done by other developers (or at the very least, someone with significant development experience.) So I could easily see how it would be classified as part of the development process.
If I had two teams, a development team and a QA team, would it be appropriate to have the QA team do code reviews instead of the development team? Or perhaps in addition to the development team? Does it differ from firm to firm? Is it just a matter of semantics?