Differences

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

--- principles:fail_fast [2013-02-25 16:16] – [Caveats] christian
+++ principles:fail_fast [2015-11-12 20:13] – [Rationale] 24.224.252.66
@@ Line 24: / Line 24: @@
 ===== 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 73: / Line 73: @@
 {{page>collections:Principles in "The Pragmatic Programmer"#Box}}
-===== Example =====
+===== Examples =====
@@ Line 91: / Line 91: @@
   * 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]].