User Tools

Site Tools


principles:easy_to_use_and_hard_to_misuse

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
principles:easy_to_use_and_hard_to_misuse [2013-06-22 20:39]
christian
principles:easy_to_use_and_hard_to_misuse [2013-08-04 14:18] (current)
christian [Complementary Principles]
Line 79: Line 79:
   * [[Invariant Avoidance Principle]] (IAP): One reason for a possible misuse of a module is an invariant. For example there might be a method which takes a list and an index where the index has to be within the bounds of the list. Each of these invariants imposes further possibilities for misuse of the module. So it is better to avoid them.   * [[Invariant Avoidance Principle]] (IAP): One reason for a possible misuse of a module is an invariant. For example there might be a method which takes a list and an index where the index has to be within the bounds of the list. Each of these invariants imposes further possibilities for misuse of the module. So it is better to avoid them.
   * [[Information Hiding/​Encapsulation]] (IH/E): A module should be properly encapsulated in order to make it easy to use and hard to misuse.   * [[Information Hiding/​Encapsulation]] (IH/E): A module should be properly encapsulated in order to make it easy to use and hard to misuse.
 +  * [[Law of Leaky Abstractions]] (LLA): The more an abstraction leaks, the less it can be considered hard to misuse.
  
 ==== Principle Collections ==== ==== Principle Collections ====
principles/easy_to_use_and_hard_to_misuse.txt · Last modified: 2013-08-04 14:18 by christian