Don't repeat yourself
In software engineering, don't repeat yourself (DRY) is a principle of software development aimed at reducing repetition of software patterns,[1] replacing it with abstractions or using data normalization to avoid redundancy.
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.[2] They apply it quite broadly to include "database schemas, test plans, the build system, even documentation".[3] 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.
DRY vs WET solutions[edit]
Violations of DRY are typically referred to as WET solutions, which is commonly taken to stand for either "write everything twice", "we enjoy typing" or "waste everyone's time". WET solutions are common in multi-tiered architectures where a developer may be tasked with, for example, adding a comment field on a form in a web application. The text string "comment" might be repeated in the label, the HTML tag, in a read function name, a private variable, database DDL, queries, and so on. A DRY approach eliminates that redundancy by using frameworks that reduce or eliminate all those edit tasks excepting the most important one, leaving the extensibility of adding new knowledge variables in one place.[4][5][6]
See also[edit]
- Abstraction principle (programming)
- Code duplication
- Code reuse
- Copy and paste programming
- Database normalization and Denormalization
- Disk mirroring
- Redundancy (engineering)
- Rule of three (computer programming)
- Separation of concerns
- Single source of truth (SSOT/SPOT)
- Structured programming
References[edit]
- ^ Foote, Steven (2014). Learning to Program. Addison-Wesley Professional. p. 336. ISBN 9780133795226.
- ^ Hunt, Andrew; Thomas, David (1999). The Pragmatic Programmer : From Journeyman to Master (1 ed.). USA: Addison-Wesley. p. 320. ISBN 978-0201616224.
- ^ Dave Thomas, interviewed by Bill Venners (2003-10-10). "Orthogonality and the DRY Principle". Retrieved 2006-12-01.
- ^ Justin Lee (2006-03-08). "DRY is for losers". Retrieved 2013-08-31.
- ^ Alex Papadimoulis (2011-12-08). "The WET Cart". Retrieved 2012-05-21.
- ^ Kevin Greer (2016-02-05). "FOAM DRY + WET". Retrieved 2016-03-09.
External links[edit]
- Don't Repeat Yourself at WikiWikiWeb
- Once and Only Once at WikiWikiWeb
- 97 Things Every Programmer Should Know (O'Reilly)
- The myth of over-normalization (discussion of academic extremes vs. real-world database scenarios)
- Wilson G, Aruliah DA, Brown CT, Chue Hong NP, Davis M, Guy RT, et al. (2014). "Best Practices for Scientific Computing". PLoS Biol. 12 (1): e1001745. doi:10.1371/journal.pbio.1001745.
Don't Repeat Yourself (or Others)
