DRY is an over-rated programming principle?
Every time I read an article like this, &quot;why &lt;often cited best practice&gt; is overrated&quot;, I think, yeah you are right in theory. But most places I have worked, these best practices were not overused, but underused. If you have the problem that your coworkers create unneccessary abstractions, I envy you, because I have so often had the opposite problem. Maybe this is not the case if you work in a great software development team. But if you work somewhere where they do software development on the side (science, hardware, etc..) it is the main issue.<p>People not able to factor out functions or structure their code in a readable way. Variables are called v1, v2, v3. Unit testing seen as a waste of time. CI seen as a fun toy. They lack the experience to even notice the difference.<p>Maybe I&#x27;m becoming a curmudgeon, but I think many people would be well served by just googling &quot;&lt;my programming language&gt; best practices&quot;, learning the acronyms like DRY, and just following them. And when you have gained some experience, sure, then you should question the wisdom and not follow it blindly.