42 ms·
Technical debt is the difference between the actual code and how you would ideally write it with today’s knowledge and no time constraints. By that definition,
by layer8 3y ago
Technical debt is the difference between the actual code and how you would ideally write it with today’s knowledge and no time constraints. By that definition, bad code is a subset of technical debt, as you presumably wouldn’t write that bad code today unless maybe under time pressure. The other kind of technical debt is when you have in principle good code but the assumptions, requirements or external conditions have changed, and thus you wouldn’t write it that way today. Your second paragraph matches that case.
- hmottestad 3y agoThat’s a good way of putting it :)