Chapter 2

Engineers mention debt, so why can't I see the cost?

Kỹ sư nói nợ, sao tôi nghe không ra giá?

The chapter's question

What do I ask so engineers can describe the debt in consequences rather than jargon?

Big idea

Engineers know where the debt is; product people need to ask so it becomes a priced choice.

In this chapter

  1. Part 2.1

    The Parts People Fear

    Which part of the code are engineers most reluctant to touch?

  2. Part 2.2

    Estimates After Paydown

    If this part were cleaned up, how much faster would upcoming work go?

  3. Part 2.3

    Recurring Bugs

    Which bugs have been fixed many times yet keep coming back?

  4. Part 2.4

    Risk of Doing Nothing

    What happens if it is still untouched a year from now?

The reading for this chapter is inside Conan School

This chapter has 4 readings, with case stories and exercises. Chapter 1 of The Debt Nobody Sees is free to read right here.

Read in Conan School

Chapters of The Debt Nobody Sees

  1. 1.Is tech debt really just an engineering problem?
  2. 2.Engineers mention debt, so why can't I see the cost?
  3. 3.Paying debt or shipping features: which ruler decides?
  4. 4.Will the boss accept fewer features this quarter?
  5. 5.Who really creates the tech debt?