Blaming bad or changing requirements, or clients not knowing what they really want vs what they really need, for messy code is a poor excuse for technical debt. Besides I'm skipping all project management flaws, even if you're a lone programmer. If a client complains for their developers not able to deal with my code (good or bad) I first apply the 3 month warranty. If the issue is my fault during that time I'll fix it. After that, or even if the code was touched by someone else, then the issue solving is treated as a new requirement and has to be paid, sorry but no working for free in those cases.
Team playing has taught me that technical debt has to be avoided since the beginning. Your future self will thank you for that, your teammates and other developers will hate you less/love you more.
Do (well) or do not. There is no try.
Embrace as a life rule that there are only 2 ways of doing things/solving problems: the right way and the wrong way. Try to do it right 😃