2 spelling and grammar
source | link

Look at exceptions.

A general strategy would be

  • when an error occurs log it; write it to a file or error database. This is useful for monitoring your application and diagnosing faults

  • if it is its recoverable therecoverable; then recover. Ensure your system is in a sane state and continue. This may involve discarding some transaction or packet. If it might be a problem log it.

  • if it isn't recoverable; allow the user to save his work and do a clean shutdown

Carrying on after the system is broken only compounds the problem.

There is no "error handling strategy" that enables recovery from bugs. Your developement process should have elimated them before the user got near your system.

There are static analysis tools and testing tools to help you find problems in your code.

Look at exceptions.

A general strategy would be

  • when an error occurs log it; write it to a file or error database. This is useful for monitoring your application and diagnosing faults

  • is its recoverable the recover. Ensure your system is in a sane state and continue. This may involve discarding some transaction or packet. If it might be a problem log it.

  • if it isn't recoverable; allow the user to save his work and do a clean shutdown

Carrying on after the system is broken only compounds the problem.

There is no "error handling strategy" that enables recovery from bugs. Your developement process should have elimated them before the user got near your system.

There are static analysis tools and testing tools to help you find problems in your code.

Look at exceptions.

A general strategy would be

  • when an error occurs log it; write it to a file or error database. This is useful for monitoring your application and diagnosing faults

  • if it is recoverable; then recover. Ensure your system is in a sane state and continue. This may involve discarding some transaction or packet. If it might be a problem log it.

  • if it isn't recoverable; allow the user to save his work and do a clean shutdown

Carrying on after the system is broken only compounds the problem.

There is no "error handling strategy" that enables recovery from bugs. Your developement process should have elimated them before the user got near your system.

There are static analysis tools and testing tools to help you find problems in your code.

1
source | link

Look at exceptions.

A general strategy would be

  • when an error occurs log it; write it to a file or error database. This is useful for monitoring your application and diagnosing faults

  • is its recoverable the recover. Ensure your system is in a sane state and continue. This may involve discarding some transaction or packet. If it might be a problem log it.

  • if it isn't recoverable; allow the user to save his work and do a clean shutdown

Carrying on after the system is broken only compounds the problem.

There is no "error handling strategy" that enables recovery from bugs. Your developement process should have elimated them before the user got near your system.

There are static analysis tools and testing tools to help you find problems in your code.