Principles Wiki

User Tools

Site Tools

You are here: Principles Wiki » Principles » Rule of Explicitness (RoE)
principles:rule_of_explicitness

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
principles:rule_of_explicitness [2013-06-22 20:40] – christianprinciples:rule_of_explicitness [2013-08-10 10:57] – [Context] christian
Line 9: Line 9:
   * [[contexts:Object-Oriented Design]]   * [[contexts:Object-Oriented Design]]
   * [[contexts:API Design]]   * [[contexts:API Design]]
 +  * [[contexts:Implementation]]
  
 ===== Principle Statement ===== ===== Principle Statement =====
Line 91: Line 91:
   * [[Murphy's Law]] (ML):The typical reason for RoE is to avoid unnecessarily complicated solutions and possibilities for defects. Don't loose that goal out of sight.   * [[Murphy's Law]] (ML):The typical reason for RoE is to avoid unnecessarily complicated solutions and possibilities for defects. Don't loose that goal out of sight.
   * [[Model Principle]] (MP): RoE states that [[anti-patterns:primitive obsession]] shall be avoided. Instead more specific types should be used in parameter lists. MP makes this even clearer: In object-orientation objects instead of plain integers or strings are used.   * [[Model Principle]] (MP): RoE states that [[anti-patterns:primitive obsession]] shall be avoided. Instead more specific types should be used in parameter lists. MP makes this even clearer: In object-orientation objects instead of plain integers or strings are used.
 +  * [[Law of Leaky Abstractions]] (LLA): Often abstractions create a level of implicitness. Abstraction leaks are one reason why explicit solutions can be considered preferable.
  
 ==== Principle Collections ==== ==== Principle Collections ====
principles/rule_of_explicitness.txt · Last modified: 2021-10-18 22:06 by christian