principles:fail_fast
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:fail_fast [2020-10-12 16:11] – old revision restored (2013-06-22 20:37) 159.69.186.191 | principles:fail_fast [2020-10-12 16:11] – old revision restored (2013-02-05 17:58) 159.69.186.191 | ||
---|---|---|---|
Line 8: | Line 8: | ||
===== Context ===== | ===== Context ===== | ||
/* fill in contexts here: */ | /* fill in contexts here: */ | ||
- | * [[contexts:Implementation]] /* FF is more about implementation than design */ | + | * [[contexts:Object-Oriented |
- | * [[contexts: | + | |
Line 32: | Line 31: | ||
* Throw an Exception. | * Throw an Exception. | ||
* Use assertions. | * Use assertions. | ||
- | |||
- | |||
- | ===== Caveats ===== | ||
- | |||
- | FF reveals problems which are already present in the system. For a system with only a few problems, this is good as the remaining faults are identified and fixed more easily. But applying FF to a system that has many problems may decrease reliability further as problems which were hidden, show up, produce error messages and lead to system aborts. | ||
- | |||
- | See also section [[#contrary principles]]. | ||
Line 70: | Line 62: | ||
==== Principle Collections ==== | ==== Principle Collections ==== | ||
+ | {{page> | ||
{{page> | {{page> | ||
{{page> | {{page> | ||
- | ===== Examples | + | ===== Example |
Line 91: | Line 84: | ||
* Joshua Bloch: // | * Joshua Bloch: // | ||
- | ===== Discussion ===== | ||
- | |||
- | Discuss this wiki article and the principle on the corresponding [[talk: |
principles/fail_fast.txt · Last modified: 2021-10-18 21:33 by christian