Don't repeat yourself

In software engineering, Don't Repeat Yourself (DRY) or Duplication Is Evil^{[citation needed]} (DIE) is a principle of software development aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures. The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system." The principle has been formulated by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. They apply it quite broadly to include "database schemas, test plans, the build system, even documentation."^[1] When the DRY principle is applied successfully, a modification of any single element of a system does not require a change in other logically-unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in sync. Besides using methods and subroutines in their code, Thomas and Hunt rely on code generators, automatic build systems, and scripting languages to observe the DRY principle across layers.

Applying DRY

Also known as Single Source of Truth, this philosophy is prevalent in model-driven architectures, in which software artifacts are derived from a central object model expressed in a form such as UML. DRY code is created by data transformation and code generators, which allows the software developer to avoid copy and paste operations. DRY code usually makes large software systems easier to maintain, as long as the data transformations are easy to create and maintain. Tools such as XDoclet and XSLT are examples of DRY coding techniques. Examples of systems that require duplicate information are Enterprise Java Beans version 2, which requires duplication not just in Java code but also in configuration files. Examples of systems that attempt to reduce duplicate information include the Symfony, web2py and Django web frameworks, Ruby on Rails application development environment and Enterprise Java Beans version 3.

Kent Beck has mentioned that he does not "subscribe to [DRY] for test code because zz[he] want[s] [his] tests to read like a story".^[2]

See also

• Abstraction principle (programming)
• Code reuse
• Single Source of Truth
• Occam's Razor
• Separation of concerns
• KISS principle
• You Ain't Gonna Need It
• Rule of three (programming)
• Redundancy (engineering)
• Mirror (computing)

References

1. ^ Dave Thomas, interviewed by Bill Venners (2003-10-10). "Orthogonality and the DRY Principle". http://www.artima.com/intv/dry.html. Retrieved 2006-12-01. 
2. ^ Kent Beck, interviewed by Martin Lippert (2010-09). "Software Engineering Radio Episode 167: The History of JUnit and the Future of Testing with Kent Beck". http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck. Retrieved 2011-01-25. 

External links

• Orthogonality and the DRY Principle
• Don't Repeat Yourself at WikiWikiWeb
• Once and Only Once at WikiWikiWeb
• 97 Things Every Programmer Should Know (O'Reilly)
• Codereflect.com - DRY Principle