principles:generalization_principle
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
principles:generalization_principle [2013-06-16 19:08] – [Strategies] from thesis christian | principles:generalization_principle [2013-06-19 12:54] – resources, links, ... christian | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Variants and Alternative Names ===== | ===== Variants and Alternative Names ===== | ||
- | * Build Generality into Software((Alan M. David: //201 Principles | + | * Build Generality into Software(({{page> |
- | * Abstractions Live Longer than Details((Andrew Hunt and David Thomas: //The Pragmatic Programmer//)) | + | * Abstractions Live Longer than Details(({{page> |
===== Context ===== | ===== Context ===== | ||
Line 40: | Line 40: | ||
===== Caveats ===== | ===== Caveats ===== | ||
- | Making a [[glossary: | + | Making a [[glossary: |
- | Another problem is the [[wp>turing tarpit]]. This means that the module is so general that arbitrarily complex tasks can be performed but those of interest, meaning the rather simple tasks that occur over and over again, are also difficult to do. This is a violation of the [[Easy to Use and hard to Misuse|EUHM]] principle. | + | Another problem is the [[anti-patterns: |
See also section [[#contrary principles]]. | See also section [[#contrary principles]]. | ||
Line 51: | Line 51: | ||
The term " | The term " | ||
- | David Parnas: //Designing Software for Ease of Extension and Contraction// | + | {{page> |
principles/generalization_principle.txt · Last modified: 2021-10-20 21:20 by christian