Ship Small Diffs
Ehh... nice in principle (and I do small deploys all the time for work), but too many artificially-small changes can easily cause you to &quot;miss the forest for the trees&quot;.  Each change is small and LGTM-able, but they can add up to a misbehaving system unless you have full context (which, because they&#x27;re small, <i>does not exist</i> in the diffs).<p>If it&#x27;s conceptually a single unit, keep it a single unit.  Pushing dead code in small pieces that waits for a small master switch doesn&#x27;t give you additional safety (though it can give you easier merges).<p>&gt;<i>Reviews for large diffs are closed with a single “lgtm,” or miss big-picture problems for the weeds.</i><p>That means you have bad reviews.  If it can&#x27;t be figured out, how was it written?  Take the time and do it right.  Yes, it&#x27;s a large commitment - is it larger than the value being created?  If no, why does it exist?