TL;DR —
Code reviews and pull requests are the basic building blocks in many software engineers' life (The Workflow) They prevent bugs, mistakes, and help distribute the knowledge around a code base in small units of changes. It is very important that we try to have a policy than addresses all these different variables, and tries to optimize the user experience (with all that it entails) and developer productivity. Have a policy. Define before hand what is the threshold to approve or reject a PR and in which cases.
[story continues]
Written by
@jsdario
CTO of Yeti Smart Home. Founder of Scope.ink & Netbeast.
Topics and
tags
tags
software-engineering|code-reviews|team-productivity|continuous-integration|test-automation|team-management|programming-languages|latest-tech-stories
This story on HackerNoon has a decentralized backup on Sia.
Transaction ID: E9vTJ-iEXnsiwKOCrTfI6_kC92B_ieP87EV-XYtlYJk
