DRY principle
The DRY principle is a best practice in programming that encourages software developers to write code once, and only once. DRY stand for "don't repeat yourself."
The principle is credited to Andrew Hunt and David Thomas, authors of "The Pragmatic Programmer." According to the authors, every discrete chunk of knowledge should have one, unambiguous, authoritative representation within a system. Once redundancies in process and logic are eliminated, technical debt will also decline.
The DRY principle facilitates the creation of software applications with reusable components and plays an important role in structured programming.
Related Terms
Read More About IT
Which programming practices alleviate code redundancy?
The DRY Principle: Benefits and Costs with Examples
Understanding the modular monolith and its ideal use cases
Refactor vs. rewrite: Deciding what to do with problem softwar
Keep In Touch
For feedback about this definition or to suggest a new definition (or learning resource) please email me or reach out to me on Twitter. Thank you for reading!