Linked from

The 15 pages that link to Technical debt, each with the reason it gives.

• Computer programmingRelated: Programming shortcuts can make later changes slower and riskier.

• Agile software developmentRelated: Rapid delivery can create maintenance costs when short-term choices are not revisited.

• Software engineeringRelated: Shortcuts can speed delivery while increasing the cost of subsequent engineering work.

• Backward compatibilityRelated: Compatibility constraints can preserve outdated design decisions and increase maintenance costs.

• PrototypingRelated: Exploratory code can become costly when a prototype is mistaken for production software.

• Modular designRelated: Poorly chosen boundaries can make cross-module changes costly and accumulate maintenance burden.

• Software architectureRelated: Architectural shortcuts can accumulate costs that make later changes harder.

• Software developmentRelated: Short-term implementation shortcuts can make later changes slower and riskier.

• RedundancyCompared with: Uncontrolled duplication can make systems harder and more expensive to change.

• Software maintenanceRelated: Accumulated shortcuts make routine maintenance slower and more hazardous.

• Ward CunninghamRelated: Cunningham introduced the metaphor to explain the costs of postponing software design improvements.

• Software portabilityRelated: Platform-specific shortcuts can reduce initial effort while making later portability costly.

• Software bugCompared with: Technical debt can make bugs harder to prevent and fix, but is not itself necessarily a bug.

• Software prototypingRelated: Promoting exploratory prototype code without revision can create costly technical debt.

• Engineering managementCompared with: It exposes a recurring management trade-off between immediate delivery and long-term engineering health.