Chapter 4

Can one big rewrite really clear the debt?

Một đợt đại tu lớn có trả được hết nợ?

The chapter's question

How do I pay down technical debt without stopping feature work?

Big idea

Paying down debt bit by bit in everyday work lasts longer than one big overhaul.

In this chapter

  1. Part 4.1

    Leave It Cleaner

    Each time I change a file, what small thing can I clean up?

  2. Part 4.2

    A Fixed Share

    What share of each cycle goes to paying down debt?

  3. Part 4.3

    Tests Before Changes

    Does the code I am about to change have tests?

  4. Part 4.4

    Rewriting From Scratch

    When is a rewrite right, and when is it a trap?

The reading for this chapter is inside Conan School

This chapter has 4 readings, with case stories and exercises. Chapter 1 of Technical Debt Charges Interest is free to read right here.

Read in Conan School

Chapters of Technical Debt Charges Interest

  1. 1.Is technical debt actually a bad thing?
  2. 2.Which debt is quietly charging us interest every day?
  3. 3.Is the boss not listening, or are we speaking code?
  4. 4.Can one big rewrite really clear the debt?
  5. 5.Who pays tomorrow for today's shortcut?