User Tools

Site Tools


principles:fail_fast

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:fail_fast [2013-02-05 17:58] – alternative names, description, relations, rationale christianprinciples:fail_fast [2013-02-25 16:16] – [Caveats] christian
Line 8: Line 8:
 ===== Context ===== ===== Context =====
 /* fill in contexts here: */ /* fill in contexts here: */
-  * [[contexts:Object-Oriented Design]] +  * [[contexts:Implementation]] /* FF is more about implementation than design */ 
 +  * [[contexts:API Design]] 
  
  
Line 31: Line 32:
   * Throw an Exception.   * Throw an Exception.
   * Use assertions.   * Use assertions.
 +
 +
 +===== Caveats =====
 +
 +FF reveals problems which are already present in the system. For a system with only a few problems, this is good as the remaining faults are identified and fixed more easily. But applying FF to a system that has many problems may decrease reliability further as problems which were hidden, show up, produce error messages and lead to system aborts.
 +
 +See also section [[#contrary principles]].
  
  
Line 62: Line 70:
 ==== Principle Collections ==== ==== Principle Collections ====
  
-{{page>collections:OOD Principle Language#Box}} 
 {{page>collections:Unix Philosophy (Eric S. Raymond)#Box}} {{page>collections:Unix Philosophy (Eric S. Raymond)#Box}}
 {{page>collections:Principles in "The Pragmatic Programmer"#Box}} {{page>collections:Principles in "The Pragmatic Programmer"#Box}}
principles/fail_fast.txt · Last modified: 2021-10-18 21:33 by christian