All these articles are fine and dandy but I would like to see more pragmatic articles on how to reduce technical debt. A lot of books have been written aroumd s

All these articles are fine and dandy but I would like to see more pragmatic articles on how to reduce technical debt. A lot of books have been written aroumd software patterns, service orientation, micro services, etc but none of them really address how to minimize technical debt over the life of software. Also not covered properly is what accounts for texhnical debt? For example, I have fee classes that have good unit tests, interfaces, proper seperation of concerns but performs really bad with 1000 concurrent users. So this goes back to how do we accurately define technical debt?