2 ms·
Based on my own experience I am quite sure that code review doesn't sacrifice velocity, it enables it. Unreviewed development has no way to ensure everyone is p
by jeffbee 4y ago
Based on my own experience I am quite sure that code review doesn't sacrifice velocity, it enables it. Unreviewed development has no way to ensure everyone is pulling in the same direction.
- cmrdporcupine 4y agoIt really, really, depends.
- marco_patino 4y agoTotally agree! Code reviews are not only for 'making sure things don't blow up $$ in production.' If your team doesn't use pair programming, code reviews are the best opportunity to share knowledge and align vision and values across the team. If you feel like code review conversations are taking too long and affecting your cycle time, then you can use the tool I created: https://pullpo.io https://pullpo.io to have these conversations on ephemeral bidirectional GitHub-Slack channels.