"Technical debt is not accidental" is a pretty bold statement in my opinion. Technical debt could be defined as all which needs refactoring. Making a mistake in

"Technical debt is not accidental" is a pretty bold statement in my opinion. Technical debt could be defined as all which needs refactoring. Making a mistake in your original system design because of an unforeseen feature, scope creep, optimization requirements as you scale, all are things that can drive up your technical debt. Conscious shortcuts are only the most obvious path to debt and they're most likely the easiest to pay back as well. Technical debt is a concept you become intimately familiar with working in the enterprise space.