Technical Debt

Technical debt can result from rushed decisions, outdated dependencies, missing tests, duplicated logic, weak architecture, or requirements that changed over time. Teams manage it by making the cost visible and prioritizing improvements alongside product work. Understanding it gives teams a shared vocabulary for building software that remains understandable and dependable as requirements change.