2 ms·
One big danger of "technical debt" is it can appear impossibly shiny. People want to work on it, despite there being high-priority features that need to be impl
by phendrenad2 6y ago
One big danger of "technical debt" is it can appear impossibly shiny. People want to work on it, despite there being high-priority features that need to be implemented, for instance. This is because technical debt is a code problem, while adding features is a business problem. Programmers like to stay in code-land.
- ornornor 6y agoAnd soon enough, implementing any new feature is impossible without breaking anything else. And it takes a month.
- phendrenad2 6y agoI actually think that fragility and the things people actually call tech debt are two different things. No one cares if an architecture is perceived as clean and elegant, but takes a long time to implement anything (due to many levels of abstraction and indirection). Just as long as it's (perceived to be) clean and elegant! Tech debt is unfortunately rarely measured or quantified, it's usually a gut instinct.