"Clean Code: A Handbook of Agile Software Craftsmanship" is a very interesting book, since it contains a lot of best practices and advices for programmers. I recommend this book to anyone who wants to improve his/her code. Here’s a fragment from the book which I find very compelling:

Infrastructure as Code (IaC) is one of the most common terms we hear alongside every DevOps tool or concept. But what is it and how can we benefit from it? Let's try to understand what IaC is all about. But first, let’s see a formal definition.

In any cases, duplicate code should be avoided, because code reuse, encapsulation and maintainability are not accomplished. If encapsulation/code reuse is made properly, then we know for sure that we won't revisit that working code (unless we need to extend it). Writing good code and following best practices avoid technical debt.