I think that this is a good exploration of what technical debt feels like, but in terms of formal quantification, I don’t think it’s as good as a short clean definition: Technical debt is the code maintained and supported by your organization, measured in lines/characters of syntax.