
2/10/2020
What this post added
This post details practical techniques for improving code reviews at Shopify, focusing on communication and process. It introduces six key practices: keeping pull requests small (around 200-300 lines affected for data engineering), using draft PRs for early feedback, adhering to one PR per concern to improve review quality and rollback atomicity, focusing on the code and not the person by offering constructive feedback and assuming best intentions, picking the right people to review based on context and expertise, and providing a clear map in the PR description with questions about necessity, beneficiaries, potential risks, alternative approaches, and affected systems. The post emphasizes that good code is not only bug-free but also useful, and that PR descriptions should tie code to team objectives.