If no one in the car factory remembers what the paint sprayer was set at, they will make a giant mess. Any definition of technical debt should encompass more t

If no one in the car factory remembers what the paint sprayer was set at, they will make a giant mess. Any definition of technical debt should encompass more than the narrow field of software engineering. I also like this definition, with the caveat that technical debt should also include things like using a "good enough" solution and being forced to use it for a long time after it becomes counterproductive because you don't want to allocate the resources to switch. Say, a payroll provider as a simplistic example.