Better Programming

Advice for programmers.

Follow publication

Member-only story

Technical Debt as a Product-Engineering Issue

Andreja Dulović
Better Programming
Published in
12 min readNov 29, 2021
Photo by Ehud Neuhaus on Unsplash

What is technical debt?

A search of the current literature reveals many definitions of “technical debt.” Here are a few examples:

Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. — From techopedia.com

Technical debt … is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. — From wikipedia.com

Technical debt … is the result of prioritizing speedy delivery over perfect code. From productplan.com

Frankly, it doesn’t add up. If we need to change something in the implementation of the code today because we made a “wrong” decision in the past, it doesn’t matter why we made that decision. Now we simply need to fix it before it does more damage.

Maybe it was a good, optimal decision at the time. Maybe a future-proof solution would have…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Andreja Dulović
Andreja Dulović

Written by Andreja Dulović

I connect technology with business and help teams grow and change. https://www.andrejadulovic.com