Only accepted work is recordedAboutGuidesContactSign in
CitePepCitePep

Technical Debt Explained: Managing Code Quality Over Time

Corrected by Emir Baycan · on When Notes Fly · 15 November 2026 · View published page ↗

Needs stronger evidence

The exact change

Before
A 2020 study by Eleni Constantinou and colleagues at the University of Antwerp analyzed technical debt accumulation in 59 open-source Java projects over their entire lifetimes, tracking debt items introduced and resolved over periods of 5 to 15 years. | The study found that debt items rarely get paid down spontaneously - only 26% of debt items identified were ever resolved, and the probability of resolution declined sharply the longer an item remained unaddressed. | Items older than two years had less than a 10% chance of resolution. The research provides empirical grounding for the intuition that debt compounds: the longer you wait, the less likely you are to pay it back.
After
Removed. | Removed. | Removed.

Suggested change

Removed 3 unsourced claims.

Why this is better

Each study and survey figure in the article was checked against the published source. Claims for which no published source could be located were removed.

More by Emir Baycan in Programming Development

All of Emir Baycan's contributions →