If you are a programmer, you likely have heard of the principle of Don’t Repeat Yourself (DRY)

It’s one of those concepts in programming that seems so natural that it is almost axiomatic and unquestionable

Given that, you may believe following the DRY principle necessarily lead to reduced technical debt

The goal of this article is to illustrate a more nuanced reality

Let’s start with a simple definition of technical debt