First of all, let me apologize for the clickbait-y title, but we need to talk about Don’t Repeat... Tagged with productivity, beginners, codenewbie.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

Don't repeat yourself (DRY is dead) is the root of all software evil, says John Sutter. Repeating yourself is basically giving yourself the time and space to come up with the right abstractions instead of engaging in guesswork and clairvoyance.

Please do repeat yourself (DRY is dead)

Totally agree with the idea. I get frustrated many times digging some “wonderfully engineered” modulesg that are used exactly once. But I think the title is a bit misleading, DRY and compromise should be considered equally to get the most suitable option. Cuz completely leaning to any of them leaves nothing but chaos.

total disagree, copy/paste is time wasting for the future, if u are cheap coder is good, if u are good coder is bad

Really feels like getting worked up over a common sense issue. Of course DRY is not a rigid principal: it’s good practice. Pushing this kind of anecdotal rant as objective truth (as the heading implies) is just harmful and not a little patronising.

I don’t need to tell you that the plural of anecdote is not “data” - a subtle mistake in your copy-pasta will creep, on little flat feet, into every aspect of your system. I don’t mind people encouraging devs to be as lazy as possible. That’s what makes us better at what we do. Encouraging inexperienced folk to be stupid as well as lazy is where I draw the line. While your stories are apt and entertaining, I believe your conclusion should be marked with a “not even wrong” surgeon general’s warning.

After all I agree to have the “common sense” to apply DRY when is the right way and identify when we could fall into a OverEngineering stuff.