Afterword by Mark Stringer
I have greatly enjoyed reading Andrew’s book on technical debt. I have spent the last 15 years or so trying to manage software development projects. I’ve seen legacy projects become unmaintainable and unmodifiable because of technical debt. And for most of that time, I’ve agreed that technical debt is a bad thing, and we should definitely do something about it. However, until I’d read this book, I’d been mostly at a loss to know exactly what it is that I, my team, or senior management could do.
Now, I have a much better idea of what I can do about technical debt, and that partly comes from a better understanding what kind of thing that debt is and where it comes from.
One thing that Andrew does beautifully in this book ...