I use a similar matra in that I don’t accumulate technical debt. When writing software I strive to write right from the start, and taking care not to end up with a tactical solution. Once in awhile, technical debt is discovered, and then I fix it immediately before continuing with planned features.

The main reason why this workflow suits me well, is that I don’t have to switch contexts to do it. Instead of spending time documenting the debt and putting it in the backlog, I would like to fix it while my brain is still focused on it.