Image for post
Image for post
Photo by Antoine GIRET on Unsplash

The saying goes…

This also applies to tech debt. The best time to address tech debt was as soon as it was identified, the second best time is now. The worst time is what most people do, say they’ll get to it.

If you’re responsible for a real system that paying customers depend on, you have, or should have, risk aversion. Any change is risky. If things are working why fix them? That’s why ignoring tech debt is very common.

However, if you address tech debt proactively, you have some measure of control in the process, that reduces the risk. If you ignore tech debt:

  • It will greatly contribute to bit rot.
  • It will eventually be mysterious or even unsupported.
  • It may require a security update.
  • It may outright fail.

These may happen independently or in combination. The moment it comes to a head and can no longer be avoided will be unpredictable and unscheduled. You will be forced to act reactively and that brings far greater risk.

So, as Nike says, just do it.

Graybeard code monkey, started on an Apple IIe, got a CS degree in the 80’s, and coded my way through C, C++, Objective-C, Java, Kotlin — and now Go.

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