Chapter 2

Why do bigger changes get approved faster?

Vì sao thay đổi càng lớn càng được duyệt nhanh?

The chapter's question

Is the change I send for review small enough to read in one sitting?

Big idea

A small change gets reviewed carefully; a large change gets approved to get it over with.

In this chapter

  1. Part 2.1

    How Many Lines

    How many lines is the team's average change?

  2. Part 2.2

    Splitting a Big Change

    Into which independent steps can a big feature be split?

  3. Part 2.3

    Describing the Change

    Does the description say why, not just what?

  4. Part 2.4

    How to Test It

    Does the reviewer know how to try this change out?

The reading for this chapter is inside Conan School

This chapter has 4 readings, with case stories and exercises. Chapter 1 of A Day in the Life of a Code Reviewer is free to read right here.

Read in Conan School

Chapters of A Day in the Life of a Code Reviewer

  1. 1.Is code review really about catching bugs?
  2. 2.Why do bigger changes get approved faster?
  3. 3.The generated code looks clean, but is it right?
  4. 4.Which review comments are rules, and which are taste?
  5. 5.What does a change cost while it waits for review?