I read the first part and I enjoyed it. I agree that us developers aren't great at communicating tech debt effectively. Managers are also not great at prioritizing it. I think the "debt" analogy has been a net negative as management often thinks "we'll just pay it later" but don't often see how much pain it's causing. So having a resource to help both sides on this topic is very valuable.

Thanks. That’s my belief as well. I would have loved to come up with a better term.

In the next two parts of the book I try to convince managers to give some autonomous time to engineers to do whatever tech debt projects they think is best. With some constraints and accountability.