DRY: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
=DRY and Coupling= | =DRY and Coupling= | ||
{{Internal|Designing_Modular_Systems#DRY_and_Coupling| | {{Internal|Designing_Modular_Systems#DRY_and_Coupling|DRY and Coupling}} | ||
=Organizatorium= | =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/ | * 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/ | ||
Revision as of 21:38, 3 January 2022
Internal
Overview
Don't Repeat Yourself - DRY: 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.
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/