DRY should be an option. Results may vary and depend on the code in question as well as the language you are using. We - a former team a couple of years ago u

DRY should be an option. Results may vary and depend on the code in question as well as the language you are using. We - a former team a couple of years ago using Java - started to duplicate code in Java, because we were totally tired of interface'ing and class'ing everything away that was not DRY. It became to tedious to bloat code with them as well as understanding whole classes when all you got was references to other interfaces etc. If there is a small service architecture like in Angular with TypeScript, abstracting away becomes fun and useful. It all depends. But what I really do not miss is the pile of interfaces in Java and C#. These became so tough to grasp and entangled, that we DRY'ed this cesspool. DRY on DRY so to say.