My takeaway from the article was, in the author's own words, "start with debt in code you’re about to change anyway". That's not to say you shouldn't tackle technical debt in code that isn't changing, rather it's lower priority.