DRY is an over-rated programming principle?
I am working in a code base right now that was literally ruined because of #3. It&#x27;s full of extremely difficult to follow and test higher order functions that are completely unnecessary. A feature request did come for a &quot;half&#x2F;half&quot; pizza and we&#x27;re spending our days trying to disentangle the higher order functions.<p>The developer who wrote this thought himself the programmer genius and wanted to make a pattern out of everything. He did not accept criticism because &quot;DRY is a holy principle&quot;.<p>And that is why a post like this is important. Because next time I have someone like him in my team I can point him to this post. Argument by Authority may be a  fallacy, but it is significantly more persuasive than other arguments.<p>And yes, you can respond to this with &quot;why did you hire this guy in the first place, or why did you not fire him?&quot;. Well I do not make all the decisions. Not every teammate is perfect. Such is reality. Particularly in such a young industry as software development which (compared to, say, electrical engineering) is still searching a common understanding of ubiquitous best practises.