Benefits of Pull Request Workflow (PR)
Want a quick and easy way to improve your developer's coding standards? Have them invite someone today for lunch!
Even if we keep our house clean and tidy, my spouse and I do up our game and spend a few additional minutes scrubbing when we have people over. Things would be lovely as is, but we still do it. Pride gets all the rooms to the next level. Having developers go through a PR (Pull Request) as a mandatory stage of the development pipeline serves the same purpose.
Peer pressure and our innate desire to look our best in front of others have immediate, positive effects on the codebase. It's an easy win.
Other great benefits await:
PRs let us shine in front of others, but we are also personally rewarded with cleaner code, which makes ongoing work more straightforward.
PRs keep in check technical debt and entropy.
PRs are one of the best tools to democratize Clean Coding best practices between your engineers.
PRs also let you learn about patterns such as the Single Responsibility Principle.
PRs share both technical and product knowledge to the team. Understanding the context allows for better decision making.
PRs leave an audit trail and document the reasoning behind some choices made.
Be proud. Use PRs to invite others into your codebase.
