| * We mostly understand the problem at hand already because we were in the same planning meeting. * We do our code reviews on GitHub by looking at the diffs. No need to pull code. * We review the code of the tests, but we don't run them. Our CI server runs tests and coverage tools. * The code is usually a short MVP, <100 lines including tests, so understanding logic and edge cases doesn't take long. * If dependencies change, it was a group discussion and we already investigated. * Again, small commits make this quick. * Small commits make this quick. * Documentation is handled by our product manager. I guess what I'm learning from reading your comment is that part of why our code reviews are fast compared to yours is that we mean drastically different things when we say "code review". |