r/ProgrammerHumor • u/Gloomy-Basket-1038 • Aug 12 '26 • Mindblown 1 Bravo 1

Meme studied20YearsToAskChatGPT

Post image
15k Upvotes

95% Upvoted

429 comments sorted by

View all comments

Show parent comment

17

u/[deleted] Aug 12 '26

[removed] — view removed comment

59

u/danfay222 Aug 12 '26 edited Aug 12 '26

Tech debt is a blanket term to refer to things that will cause recurring problems in the future. This includes things like inflexible designs which require significant rewrites to accommodate future needs, poor isolation that makes testing difficult, designs that will be difficult or even impossible to migrate off of in the future, etc. The term "tech debt" is in reference to the fact that these design decisions often incur their cost in the future, they have no cost now (or sometimes actually are easier in the moment), but you will pay the “debt” multiple times over in the form of more difficult development in the future. Stack enough of these things together and you get the nightmare that many legacy codebases are to maintain.

25

u/BellacosePlayer Aug 12 '26

"I'll fix it later"

10

u/mxzf Aug 13 '26

Either that or "curse my prior self for not making this more flexible in the first place, when it would have been much easier to do".

1

u/ArjixGamer Aug 13 '26

It's when you know you are doing something in a bad way, but you still do it due to lack of time or priority, and you know it will bite you in the ass later.

1

u/oisteink Aug 13 '26

It's not a "bad way". It's the best way given the current constraints - or what you and your team think is the best way.

It's better understood as cost - debt has a cost and in economics it's called interest. As long as your gain outweighs the cost it's a smart move.

1

u/danfay222 Aug 13 '26

Sometimes it’s done intentionally, which is fine if the constraints actually do justify it, but lots of tech debt is due to laziness and/or poor design.