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, ...

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
About the Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY) principles
DRY not WET! "Don't Repeat Yourself!"
Source
Wikipedia
Copyright information
Text from Wikipedia and Wiktionary web pages quoted for educational purposes is subject to the Wikipedia Creative Commons Attribution ShareAlike Licence
Snippet kind
INFO
Keywords
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.
Full quote
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.
URL
Don't repeat yourself
Next snippet
WET: The opposing view to DRY is called WET, a backronym commonly taken to stand for write everything twice (alternatively write every time, we enjoy typing or waste everyone's time).
Related snippets
"Don't repeat yourself" (DRY) is a principle of software development aimed at reducing repetition of information which is likely to change, replacing it with abstractions that are less likely to change, or using data normalization which avoids redundancy.
Related snippets (backlinks)
Visit also
Visit also (backlinks)