principles:rule_of_explicitness
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:rule_of_explicitness [2013-08-10 10:57] – [Context] christian | principles:rule_of_explicitness [2020-10-12 16:35] – old revision restored (2017-01-09 20:48) 159.69.186.191 | ||
---|---|---|---|
Line 34: | Line 34: | ||
* Avoid highly configurable modules. Instead implement varying behavior explicitly. | * Avoid highly configurable modules. Instead implement varying behavior explicitly. | ||
* Explicitly state which module to use | * Explicitly state which module to use | ||
- | * Avoid importing all classes of a given package/ | + | * Avoid importing all classes of a given package/ |
* Avoid '' | * Avoid '' | ||
* Explicitly name parameters | * Explicitly name parameters | ||
Line 89: | Line 89: | ||
* [[Keep It Simple Stupid]] (KISS): Explicit solutions are often also simpler. | * [[Keep It Simple Stupid]] (KISS): Explicit solutions are often also simpler. | ||
- | * [[Murphy' | + | * [[Murphy' |
* [[Model Principle]] (MP): RoE states that [[anti-patterns: | * [[Model Principle]] (MP): RoE states that [[anti-patterns: | ||
* [[Law of Leaky Abstractions]] (LLA): Often abstractions create a level of implicitness. Abstraction leaks are one reason why explicit solutions can be considered preferable. | * [[Law of Leaky Abstractions]] (LLA): Often abstractions create a level of implicitness. Abstraction leaks are one reason why explicit solutions can be considered preferable. |
principles/rule_of_explicitness.txt · Last modified: 2021-10-18 22:06 by christian