DEV Community

Discussion on: 7 Ways to Dramatically Reduce Your Time in Code Review

Collapse
 
jsuddsjr profile image
John Sudds

I have also noticed that PRs created from pair programming sessions also tend to take less time, since much of the architecture discussion happened as the code was written.

You can also use a shared .editorconfig and git hooks to verify linting is done before any files show up in the PR. Verifying in the CI pipeline is also good, but a little too late in the process for my taste. I want to know right away when I've wandered from the team's style guidelines.