DRY: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
=Internal= | =Internal= | ||
* [[Software Engineering]] | * [[Software Engineering]] | ||
* [[Designing_Modular_Systems#DRY_and_Coupling | * [[Designing_Modular_Systems#DRY_and_Coupling|Designing Modular Systems]] | ||
=Overview= | =Overview= | ||
Revision as of 22:02, 3 January 2022
External
- Pragmatic Programmer, The: From Journeyman to Master by Andrew Hunt and David Thomas
Internal
Overview
Don't Repeat Yourself (DRY) principle sys: "Every piece of knowledge should have a single, unambiguous, authoritative representation within a system."
If you are in the position to write the second time the same behavior (copy-and-paste) that means the behavior belongs into a reusable function. Duplication forces people to make a change in multiple places, and that is not good.
DRY and Coupling
Organizatorium
- The "rule of three" for software reuse suggests the you should turn something into a reusable component when you find three places that you need to use it. https://blog.codinghorror.com/the-delusion-of-reuse/ Facts and Fallacies of Software Engineering https://www.amazon.com/exec/obidos/ASIN/0321117425/