3 ms·
If we look at the wikipedia page about technical debt, there is a long list of possible causes of technical debt. To site some examples: Insufficient up
by karmakaze 6y ago
If we look at the wikipedia page about technical debt, there is a long list of possible causes of technical debt.
To site some examples:
Insufficient up-front definition
Lack of clear requirements before the start of development
Lack of documentation
Lack of a test suite
Lack of collaboration / knowledge sharing
Lack of knowledge/skills resulting in bad or suboptimal code
Poor technical leadership
Last minute specification changes
Notice that these issues are called 'technical debt' because they can have a similar outcome as technical debt. They can create a bottleneck.
But why the hell would we call these issues technical debt?
These issues are self-explanatory. Calling them technical debt not only seems inappropriate, it just obfuscates the cause of these problems and it doesn't provide any new insight.
None of those were called 'tech debt'--they were cited as common causes. How each case is handled may lead to tech debt.
- srtjstjsj 6y agoPlease don't use indentation for blockquote. HN markdown (and most other markdown) doesn't support that.