Commit and merge rates
Regular commits to source control is something that should be widely encouraged and deeply embedded within your ways of working. Having source code sitting on people's workstations or laptops for prolonged periods of time is very risky and can sometimes lead to duplication of effort or, worse still, might block the progress of other engineers.
There might be a fear that if engineers commit too frequently, the chance of defects being created increases, especially when you think there's an outside risk that unfinished code could be incorporated into the main code branch. This fear is a fallacy. No engineer worth their salt would seriously consider doing such a thing—why would they? If you have checks and balances in place, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access