3 ms·
The missing data in that research is org size. If you've got 5-10 developers in a group, I don't see any of this making much difference in anyone's productivity
by eschneider 3y ago
The missing data in that research is org size. If you've got 5-10 developers in a group, I don't see any of this making much difference in anyone's productivity. OTOH, if you're in an org with 100+ developers and every merge that goes in before you means some sort of conflict resolution, then yes, this might actually be important.
- bluGill 3y agoIf you have 100+ developers you should segregate your system so that merge conflicts outside your group of 10 are rare. Sure someone needs to upgrade a build tool and that may sometimes mean changing everything, but those are not common operation and only a few people out of your 100 ever feel that pain. (having been there, it is often best to announce it in advance and then merge Saturday when everyone else is at home - my company will let me take a different day off in the week if I work a saturday)