Chapter 3

Is the boss not listening, or are we speaking code?

Sếp không hiểu, hay mình nói sai ngôn ngữ?

The chapter's question

How do I present technical debt to people who do not read code?

Big idea

Bosses cannot buy the word refactoring, but they can buy working hours and risk.

In this chapter

  1. Part 3.1

    Converting to Hours and Money

    How many hours a month does this debt cost?

  2. Part 3.2

    The Risk of Not Paying

    What happens if the only person who understands this part leaves?

  3. Part 3.3

    A Bounded Proposal

    How many days do I need, and how will I measure the result?

  4. Part 3.4

    Telling It Through an Incident

    Which recent incidents originated from this debt?

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?