Differences

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

--- principles:fail_fast [2021-09-02 12:02] – old revision restored (2021-05-19 11:17) 65.21.179.175
+++ principles:fail_fast [2021-10-18 21:33] (current) – +++ restored +++ christian
@@ 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 90: / Line 90: @@
   * Jim Gray: //[[http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.110.9127|Why Do Computers Stop And What Can Be Done About It?]]//
   * 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]].