Author very clearly says sloppy code is 'slop', not technical debt: Technical debt is not sloppily written code. It is clean code that is less than optimal. If

Author very clearly says sloppy code is 'slop', not technical debt: Technical debt is not sloppily written code. It is clean code that is less than optimal. If you're asking what we do with slop -- how do we categorize it in planning and do we fix as we go or do we call out a task to clean up -- that's a good question. He sort of touched on it with the Holmes-on-Homes parallel.