Technical Debt

Technical debt (also known as design debt[citation needed] or code debt) is a neologistic metaphor referring to the eventual consequences of poor software architecture and software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy.As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation.
Posts about Technical Debt

No posts yet

Please check again later.
Get the top posts daily into your mailbox!