principles:fail_fast
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| principles:fail_fast [2013-06-22 20:37] – christian | principles:fail_fast [2015-11-12 20:13] – [Rationale] 24.224.252.66 | ||
|---|---|---|---|
| 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. |
principles/fail_fast.txt · Last modified: 2021-10-18 21:33 by christian