No, focus on pushing the right solution. If you hold off pushing code that works but does not solve the correct (actual) problem, that's good. Tracking commit

No, focus on pushing the right solution. If you hold off pushing code that works but does not solve the correct (actual) problem, that's good. Tracking commit frequency is one step away from tracking lines of code. If this is really the metric of performance, then you are a cog. My take would be: plan upfront consistently. What do you need to do now to unblock the work later? Does the solution make sense? Is there something more useful? Think lots, talk lots, commit sometimes.