Skip to content

Latest commit

 

History

History
26 lines (18 loc) · 1.07 KB

File metadata and controls

26 lines (18 loc) · 1.07 KB
title code review basics
date 2017-11-17
captured 2017-11-17 16:57:26 UTC
tags
code-review
git
team-practices
source GitHub issue #333
aliases
status refined

Context

A Vietnamese article on Kipalog covering the fundamentals of starting code review as a team practice, focusing on the initial hurdles and mindset shifts needed.

Source: Bật Đèn: Khi Chỉ Đâu lam Code Review

Key points

Code review is a team practice where peers examine each other's code changes before merging. The article covers the common resistance teams face when introducing code reviews and practical approaches to making them a habit.

The main benefits: catching bugs early, sharing knowledge across the team, maintaining code consistency, and building a culture of quality. The main barriers: time pressure, ego, and lack of process.

Related

  • [[effective-code-reviews]] - deeper dive into making code reviews efficient
  • [[writing-good-commit-messages]] - good commits make reviews easier