Technical debt is a new metaphor that refers to a sloppy software architecture and the consequences of unsatisfying software development. It is also referred to as “design debt”.
What kind of technical debt is there?
– Low coverage or no written test code
– Findings that smooth sharing has not been done between developers and stakeholders.
– Ignored compiler warnings and code analysis results
– Designs and codes that are unnecessarily complex
– Code not in compliance with coding conventions
– Unwanted odor (this metaphor is often used for refactoring)
– Old versions of languages and frameworks
– Difference between development environment and production environment
