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 revision Previous revision
Next revision
Previous revision
principles:fail_fast [2013-05-19 22:09]
127.0.0.1 external edit
principles:fail_fast [2015-11-12 20:13]
24.224.252.66 [Rationale]
Line 24: Line 24:
 ===== Rationale ===== ===== Rationale =====
  
-Then a failure remains undetected, it propagates through the system ultimately causing other modules to fail. This results in in a more complicated fault removal. Furthermore undesired side effects like corrupted files may occur. A crashed program clearly communicates that there is a problem and is often a better situation than a misbehaving program.+When a failure remains undetected, it propagates through the system ultimately causing other modules to fail. This results in in a more complicated fault removal. Furthermore undesired side effects like corrupted files may occur. A crashed program clearly communicates that there is a problem and is often a better situation than a misbehaving program.
  
  
Line 91: Line 91:
   * Joshua Bloch: //​[[http://​www.infoq.com/​presentations/​effective-api-design|How to Design a Good API & Why it Matters]]//   * Joshua Bloch: //​[[http://​www.infoq.com/​presentations/​effective-api-design|How to Design a Good API & Why it Matters]]//
  
 +===== Discussion =====
 +
 +Discuss this wiki article and the principle on the corresponding [[talk:​principles:​Fail Fast|talk page]].
principles/fail_fast.txt · Last modified: 2015-11-12 20:13 by 24.224.252.66