this post was submitted on 02 Feb 2026
16 points (83.3% liked)

Programming

25924 readers
314 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

To be clear: I do not think we should actually forget technical debt. Also, this is not the nth post discussing if “debt” is an appropriate metaphor. I do not have a strong opinion regarding the metaphor. My point is rather that I realized in a recent discussion that in the end, it is not so much about technical debt but rather about something else, and I wanted to share the thought.

you are viewing a single comment's thread
view the rest of the comments
[–] Feyd@programming.dev 9 points 1 month ago (1 children)

The reason we use it is to tell non-technical management people why implementing a simple feature might take an hour on a fresh project and a week on an old legacy project.

Yes, thank you. It's really as simple as that

A client recently approached me with the need to measure technical debt.

The writer made the whole essay because saying "just ask your engineers what they need to improve" wouldn't make him money.

[–] squaresinger@lemmy.world 4 points 1 month ago

The writer made the whole essay because saying “just ask your engineers what they need to improve” wouldn’t make him money.

I wonder if the writer ever worked as an engineer.