Re:Code reviews aren’t just for catching bugs
by jaimeyap on Thursday May 12, 2016 @03:03PM
(#11685888)
This is generally why smaller changes are better. They are more easily reviewed, and more easily "steered" as you put it by a good review.
And of course having a design doc ahead of time that the team can review and comment on for a longer, more complicated change, is a great thing to do. And compliments the subsequent code review[s].
And of course having a design doc ahead of time that the team can review and comment on for a longer, more complicated change, is a great thing to do. And compliments the subsequent code review[s].