The term technical debt can be misleading and confusing. It is generally referred to as a metaphor referencing the consequences of system design or software architecture in a codebase. Technical debt can be difficult to identify directly so developers need to use clues that can be broken down into social cues, code cues, and testing/deployment cues.
The post How to Identify Technical Debt appeared first on Complete Developer Podcast.
📆 2016-03-10 07:00 / ⌛ 00:53:28
📆 2016-03-03 07:00 / ⌛ 00:46:52
📆 2016-02-25 07:00 / ⌛ 00:56:00
📆 2016-02-18 07:00 / ⌛ 00:55:24
📆 2016-02-11 07:00 / ⌛ 00:53:52