News for hackers. Stuff that matters.

Tech Debt Is a Myth

In a few years from now, all the agile thought leaders (Kent Beck, Martin Fowler etc) will all start saying how tech debt is actually a myth... but you heard it from me first!!! (Okay, I have no idea what Kent Beck or Martin Fowler will be talking about in a few years from now)

But tech debt IS a myth. There are only 2 states of your tech estate:

- what you have now

- what you're about to build next.

The notion of "what could have been" or what (in the opinion of an engineer) "should have been" doesn't exist.

EG: If hard-coding a list of values delivers the functionality needed in the time-frame demanded, great! Good job! That's kinda why we invented computers. Could it have been done differently? Sure, but who cares? And if that code stays unchanged and working for a decade, brilliant, great ROI... and don't worry, the universe has a way of telling you if, in time, you need to refactor the code.

It's simple, just focus on the next top priority and stop worrying about mythical tech debt, because it doesn't exist...

( 2 comments | 2 points | on HN )
Re:Tech Debt Is a Myth by tcarnell on Monday June 03, 2024 @07:54AM (#40561776)
After thought:

Tech Debt is NOT a badge of honour, it's the opposite, it says "we made an engineering decision so bad that we now have to spend time and effort fixing/changing things which adds ZERO business value".

Re:Tech Debt Is a Myth by pawjast on Monday June 03, 2024 @08:02AM (#40561837)
This definitions belongs in dictionary!

Fixing tech debt is generally zero business value activity but it often exists because of other business constrains such as delivery time or budget.

So as much as annoying it is, it's inevitable that some tech debt exists in most of the situations.