There is some debate going on over what exactly technical debt means to a software project. The main issues seem to be what makes up technical debt and whether it should ever be acceptable to take it on. Dirty Code Is Not Technical Debt I do not believe authoring dirty code or code without corresponding tests should be considered technical debt at all. However, I do sympathize in that the debt analogy still makes sense.