User Tools

Site Tools


principles:rule_of_explicitness

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
principles:rule_of_explicitness [2017-01-09 20:43]
148.80.254.2 [Strategies] Added a mention of not importing entire namespaces for C++
principles:rule_of_explicitness [2017-01-09 20:48] (current)
148.80.254.2 [Complementary Principles] spelling and grammar
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'​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 ​lose sight of that goal.
   * [[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.   * [[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: 2017-01-09 20:48 by 148.80.254.2