loading...

Discussion on: I refuse to work in teams without a proper code review process - and you should too!

Collapse
joshcheek profile image
Josh Cheek

A good tool for brownfield projects and important code (code with high risk like db schema changes, or that has matured and stabilized and become a dependency of lots of other code). And, I guess, the way you describe it (approx a PR/code review per commit), it's not too onerous.

There are contexts, though, where the cost of code review is high, and the value is low (and sometimes even negative), so don't be too religious about it.