I might believe that to some extent except that not all development jobs lend themselves equally to cranking out commits. Sure, if you're working on a well defi

I might believe that to some extent except that not all development jobs lend themselves equally to cranking out commits. Sure, if you're working on a well defined feature with all dependencies already built, you can really crank stuff out. However, those also tend to be the easiest jobs filled by junior developers. Solving the less well understood/defined problems often generated fewer commits per day but often generates more value.