Differences

This shows you the differences between two versions of the page.

--- principles:don_t_repeat_yourself [2025-08-28 07:00] – created hildegardlahey6
+++ principles:don_t_repeat_yourself [2025-08-31 14:09] (current) – old revision restored (2021-10-18 21:27) christian
@@ Line 1: / Line 1: @@
-There’s a new modern garden hammock seat ([[https://telegra.ph/Embrace-Serenity-The-Cacoon-Hanging-Tent-Experience-08-14|great post to read]]) stealing the spotlight: the cocoon chair — and it’s easy to understand why. These wraparound wonders offer a hug-like vibe that screams comfort,  Cacoon hanging pod making them a top pick for laid-back luxury living.
+====== Don't Repeat Yourself (DRY) ======
-Originally seen in mid-century homes, cocoon chairs were made to enclose the sitter, giving you your own private bubble — even in busy spaces. Today’s versions come in plush fabrics, often paired with bouclé cushions.
+===== Variants and Alternative Names =====
-From open-plan apartments to stylish offices, cocoon-style seating is being used to create retreat corners.
+  * Single Point of Truth (SPOT)
+  * Single Source of Truth (SSOT)
-**Why They Work:**
+===== Context =====
-- Curved lines that feel safe
-- Built-in quiet zone effect
-- Bold shapes that photograph well
-- 70s revival with 2025 relevance
-(Image: [[https://jpcdn.it/img/small/d0e80bb049ffaf465c052cdc2d609668.jpg|https://jpcdn.it/img/small/d0e80bb049ffaf465c052cdc2d609668.jpg]])Designers and style-savvy homeowners are using cocoon chairs to break up open spaces. Add a floor lamp and a rug — you’ve got a design statement.
+  * [[contexts:Object-Oriented Design]]
+  * [[contexts:Implementation]]
+===== Principle Statement =====
-[[//www.youtube.com/embed/Zfc-FZK2DkA|external frame]]Looking to buy? We’ve curated retro-futuristic pods that wrap you in style and comfort.
+> "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system."((Andrew Hunt and David Thomas: //The Pragmatic Programmer: From Journeyman to Master//; see [[http://pragprog.com/the-pragmatic-programmer/extracts/tips|List of Tips]].))
+===== Description =====
+DRY not only states that code duplication shall be avoided. Rather DRY is a general rule that states that if there is duplication, there shall be some "single source of truth". Also when one piece of information has several representations (like an object structure corresponding to a database schema) DRY demands one and only one representation being the definitive one. The other representations have to be generated automatically. The "one and only" representation can be one of the used representations or alternatively a third one.
+===== Rationale =====
+If there are several representations of the same information (be it code or any other form of information), all of them have to be maintained separately while changing at the same time. There is the danger that at some point in time the different representations diverge which is a fault. But if there is a single source of truth, there is only one place where changes have to be applied. Then the representations cannot diverge.
+===== Strategies =====
+  * Add a new invokable module (a function, a method, a class, etc.) instead of duplicating code
+  * Factor out a common base class
+  * Use code generation when information has to be represented in multiple forms
+  * Use polymorphism to avoid repeatedly enumerating a set of possible solutions in if or switch statements
+===== Caveats =====
+See section [[#contrary principles]].
+===== Origin =====
+{{page>resources:The Pragmatic Programmer#reference}}
+===== Evidence =====
+/* Comment out what is not applicable and explain the rest: */
+/*  * [[wiki:Proposed]]*/
+  * [[wiki:Examined]]: There is extensive research on code cloning, its reasons, automatic detection of code clones, their evolution, etc. In ((Chanchal Kumar Roy and James R. Cordy: //[[http://citeseerx.ist.psu.edu/viewdoc/summary;jsessionid=EBC3E3E783AE0B5DEF75B9EDD4F1C9E2?doi=10.1.1.62.7869|A survey on software clone detection research]]//)) Chanchal Kumar Roy and James R. Cordy present a 115 page survey on the state of research as of 2007. Many unanswered questions remain and research is still ongoing. In 2009 Juergens et al. ((Elmar Juergens, Florian Deissenboeck, Benjamin Hummel, and Stefan Wagner //[[http://www4.in.tum.de/~deissenb/publications/2009_juergens_inconsistens_clones.pdf|Do code clones matter?]]//)) analyzed fife systems written in C#, Cobol and Java each between around 200 and 500 kLOC. They identified clones and intentionally and unintentionally inconsistent changes to them. They then related the faulty clones to them and came to the expected conclusion that clones are changed inconsistently and that this results in faults. So at least the part of DRY about code duplication is supported by research findings.
+  * [[wiki:Accepted]]: It is generally agreed upon that code duplication is to be avoided. On the other hand the broader meaning of DRY which results in the heavy use of code generators is often not considered. On the other hand //The Pragmatic Programmer// is a well known book which makes DRY a well-known and accepted principle.
+/*  * [[wiki:Questioned]]*/
+===== Relations to Other Principles =====
+==== Generalizations ====
+  * [[Murphy's Law]] (ML):Duplication is a typical example for error possibilities. In case of a change, all instances of a duplicated piece of information have to be changed accordingly. So there is always the possibility to forget to change one of the duplicates. DRY is the application of ML to duplication.
+==== Specializations ====
+  * [[Once And Only Once]] (OAOO): This is the aspect of DRY which is concerned with the avoidance of (code) duplication.
+  * [[Single Choice Principle]] (SCP): Duplication can also be duplication of information about a set of possibilities. The SCP is about this aspect.
+  * [[Write Code That Writes Code]]: This is the code generation aspect of DRY.
+==== Contrary Principles ====
+  * [[Keep It Simple Stupid]] (KISS): Especially code generators can be very complex.
+==== Complementary Principles ====
+  * [[Generalization Principle]] (GP): A generalized solution avoids duplication.
+==== Principle Collections ====
+{{page>collections:OOD Principle Language#Box}}
+{{page>collections:Principles in "The Pragmatic Programmer"#Box}}
+===== Examples =====
+===== Description Status =====
+/* Choose one of the following and comment out the rest: */
+/*[[wiki:Stub]]*/
+[[wiki:Incomplete]]
+/*[[wiki:Complete]]*/
+===== Further Reading =====
+  * [[wiki>DontRepeatYourself]]
+  * [[wp>Don't repeat yourself]]
+  * [[http://programmer.97things.oreilly.com/wiki/index.php/Don't_Repeat_Yourself|97things: Don't_Repeat_Yourself]]
+===== Discussion =====
+Discuss this wiki article and the principle on the corresponding [[talk:principles:Don't Repeat Yourself|talk page]].
-Shop the latest — and prepare to get cosy.