Technical Debt Charges Interest
Who this book is for
Người làm công nghệ và AI trong doanh nghiệp Việt Nam: nhân viên IT một mình hay trong nhóm nhỏ, lập trình viên, người dựng tính năng AI, trưởng nhóm kỹ thuật ở công ty vừa và nhỏ; vừa phải giữ hệ thống chạy ổn, vừa được giao đưa công cụ và AI mới vào công việc của các phòng khác.
Sound familiar?
- Small fixes take a day because old code is feared.
- Only one person understands the core and they are leaving.
- Management sees features, not time lost to tangled code.
- Unsupported libraries stay with no replacement plan.
After reading, you can
Help tech staff find the costliest technical debt and win time to pay it down.
Each chapter answers one question
Chapter 1: Is technical debt actually a bad thing?
What debts is my system carrying?
Technical debt is not bad; debt nobody records is.
Chapter 2: Which debt is quietly charging us interest every day?
Which debt is eating the most working hours?
Whether a debt is expensive or cheap depends on how often you have to pass through it.
Chapter 3: Is the boss not listening, or are we speaking code?
How do I present technical debt to people who do not read code?
Bosses cannot buy the word refactoring, but they can buy working hours and risk.
Chapter 4: Can one big rewrite really clear the debt?
How do I pay down technical debt without stopping feature work?
Paying down debt bit by bit in everyday work lasts longer than one big overhaul.
Chapter 5: Who pays tomorrow for today's shortcut?
How does my team decide to take on new debt?
A loan recorded when it is taken is much easier to repay than one discovered later.