principles:fail_fast
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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 ===== | ===== 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: // | * Jim Gray: // | ||
* Joshua Bloch: // | * Joshua Bloch: // | ||
+ | |||
+ | ===== Discussion ===== | ||
+ | |||
+ | Discuss this wiki article and the principle on the corresponding [[talk: | ||
principles/fail_fast.1630576962.txt.gz · Last modified: 2021-09-02 12:02 by 65.21.179.175