Brilliant talk! The “debt” metaphor in “tech debt” is problematic. Code quality is best seen as a continuous process, which needs to be supported by frequent delivery, appropriate timeframes, continuous learning, transparency and advocacy.
Good systems tend to have a lot of redundancy (“fall-backs”), and thus, have some inefficiency. Designers often seem to understand this better than engineers.