A core purpose of code review is to improve code quality by finding bugs and ensuring consistency with the project's style and standards — including consistent naming conventions, which keep the codebase readable and maintainable (option C). Reviews are meant to happen before code is merged into source control, not after (A is wrong), and 'never slowing code to production' (B) contradicts review's quality-gate role. Requiring a specific technical lead's sign-off (D) is a team policy, not a general principle of the review process.
Community Discussion