3 ms·

Code reviews can significantly sped up by pair programming a lot! When you wrote the code together, a lot of these doesn't even come up, because you discussed

• InfamousRece 2y ago
  And if you need more than 1 reviewer just do (n+1)-tuple programming (where n is the number of reviewers needed). The more the merrier!
  • shakezula 2y ago
    I think you're joking but there was a company in my area that famously stuck by their "mob programming" approach where 5+ developers would sit in a room, 1 would drive, and the rest would fill out an adjoining document.
• mook 2y ago
  Often I find reviews are useful precisely because of the distance the reviewer has to the code; a fresh set of eyes is good to catch issues. (Frequently I'd go over my own changes before submitting for review for the same reason). Pair/group programming also often ends up lacking in notes on what the thing was actually meant to be doing (because this was communicated verbally and never written down in reviews), which makes code archeology difficult. Or maybe that's just derived from the (external) code base I had to deal with that was done that way and doesn't generalize…