Four Strategies for Managing Technical Debt

Refactoring for Software Design Smells: Managing Technical Debt
The vicious cycle of technical debt

Managing technical debt

1. Identify and track the debt

2. Prioritize smells

3. Plan small refactoring installments in each iteration

4. Motivate and reward people for maintaining quality

“People care about the things that you measure and you reward.”

Related reading

  1. Book — Refactoring for Software Design Smells
  2. A Taxonomy of Software Smells

--

--

--

Student of life; student for life. Researcher, developer, and (co-)author of 'Refactoring for Software Design Smells'. Asst. prof@DAL. http://www.tusharma.in

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Tips on Logical Reasoning Test on Statements & Arguments

Rocket LegaSuite Web

API3DAO Core Technical Team Development Report, May 2021

DREAM HOST REVIEW

DATA WAREHOUSE : Hive!

Multi-Platform App Development Using SwiftUI, and Flutter: The Similarities and the Differences [+…

In search for a different perspective

Keeping multiple maps in sync in query and index in CosmWasm smart contracts with `IndexedMap`

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tushar Sharma

Tushar Sharma

Student of life; student for life. Researcher, developer, and (co-)author of 'Refactoring for Software Design Smells'. Asst. prof@DAL. http://www.tusharma.in

More from Medium

The top 4 secrets of awesome pull request

The Focus Shift from Individual Contributor to Engineering Manager

Tips for Jira + GitHub/Git repositories — Best practices for visibility of your work in…

Why you should estimate development tasks not stories