In this post, we’ll explore what DRY means, why it’s important, how to implement it, and where it’s sometimes okay to bend the rule.

What is the DRY Principle?

The DRY principle was first introduced by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. It states:

"Every piece of knowledge must have a single, unambiguous, authoritative representation within a system."

In simpler terms, don’t write the same code, logic, or data structure more than once. If you find yourself copying and pasting code or logic, it’s time to refactor.

Repetition is a Code Smell

Repetitive code might seem harmless at first, but it comes with hidden costs:

• Harder maintenance: Changing logic in one place means you have to hunt it down in other places.
• Increased bugs: Forget to update a duplicated block? Boom — inconsistent behavior.
• Bloated codebase: Repeated logic increases file size and reduces readability.

DRY in Action: Examples

Example of Repetition (Violates DRY):

function getUserDetails(user) {
  return `${user.firstName} ${user.lastName}`;
}

function displayWelcomeMessage(user) {
  return `Welcome ${user.firstName} ${user.lastName}!`;
}

Here, we're repeating the logic to concatenate the user's first and last names.

Refactored Code (Follows DRY):

function getFullName(user) {
  return `${user.firstName} ${user.lastName}`;
}

function displayWelcomeMessage(user) {
  return `Welcome ${getFullName(user)}!`;
}

Now, we have a single source of truth for the full name, making the code easier to maintain and less error-prone.

How to Apply DRY in Real Projects

• Functions/Methods: Move reusable logic into separate functions.
• Constants: Don’t repeat magic strings or numbers — use constants.
• Components: In front-end frameworks like React or Vue, extract common UI elements into reusable components.
• Database Schemas: Use shared models or schema definitions where possible.
• Configurations: Avoid duplicating environment variables or app settings.

But Wait — Don’t Overdo DRY!

Like any principle, DRY has its limits. Over-abstraction can lead to "pseudo-clever" code that’s hard to read and maintain. This is known as "AHA" (Avoid Hasty Abstractions).

Rule of Thumb:

First duplication is a sign. Second is a warning. Third is time to refactor.

Conclusion

The DRY principle is a cornerstone of clean code. By reducing repetition, you make your codebase leaner, easier to understand, and more maintainable. Just remember to balance DRY with readability and real-world practicality.

Have you spotted any repetition in your code lately? Maybe it’s time for a little DRY refactoring. 😉