Coding by exception
 | This article needs additional citations for verification. (May 2014) |
Coding by exception is an anti-pattern and an accidental complexity in which an exception is allowed and used to continue a software system. This anti-pattern can quickly degrade software in performance and maintainability.[1]
As a general rule, well designed software projects contain very few corner cases[2]. There are a variety of software development methodologies that purport to help engineers develop software that avoid these corner cases. They typically address dependency management issues. Design patterns are another tool for arriving at less of a 'one-off' solution.
Accidental Complexity
Accidental complexity is that complexity which arises in computer programs or the development process which is deemed not essential to the problem being solved. Coding by exception is an example of accidental complexity. Where this issue arises from poor planning or programming, some complexity is essential: essential complexity and unavoidable. Here is a list[3] of accidental complexities:
- Blind Faith
- Error Hiding
- Hard Coding
See also
=References
 | This computer science article is a stub. You can help Wikipedia by expanding it. |