Managing Technical Debt

  • de Kort W
N/ACitations
Citations of this article
4Readers
Mendeley users who have this article in their library.
Get full text

Abstract

If you have worked long enough as a software developer, you have definitely wished that you could start a project totally from scratch. Throw away all the messy code and build it from scratch with all the knowledge you have now. But why is it that code becomes messy? We even have specific terms to describe it—code rot, big ball of mud, spaghetti code. These terms all describe that code will become a mess when not carefully controlled and monitored.

Cite

CITATION STYLE

APA

de Kort, W. (2016). Managing Technical Debt. In DevOps on the Microsoft Stack (pp. 137–160). Apress. https://doi.org/10.1007/978-1-4842-1446-6_8

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free