How in your team do you enforce / encourage code reviews so that they are an embedded part of your process? Do you have anything like a "triviality threshold" for updates which are so trivial that they don't need to be reviewed? How do you avoid devs just "ticking a box" so they can get on with their own work?
submitted by /u/diego_muk
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/2Dpmp7G
Ameer Academy 