Things go wrong
Files are missing, networks drop, users type nonsense, divisions land on zero. A robust program anticipates errors and handles them, instead of crashing in the user's face. Error reporting differs by language: exceptions, explicit return values and result types require different handling. Check the example and language notes before choosing a recovery strategy.
try {
int n = Integer.parseInt("abc");
} catch (NumberFormatException e) {
System.out.println("Bad input: " + e.getMessage());
}When to catch
Only catch errors you actually know how to recover from. Catching and then ignoring an error is the single most common cause of mysterious bugs in production systems — the program keeps going as if everything were fine while the data is silently broken.
Logging
Whenever you catch an error, log it with enough context (what you were trying to do, with what inputs) that someone reading the log later can understand what happened. Modern apps live or die by the quality of their logs.
Details for java
Checked exceptions must be caught or declared. NumberFormatException is a runtime error requiring an input policy. Catch failures you can explain instead of returning a fabricated answer.
Practice and verify
Change one meaningful value in the example and predict the result before running. Then test a boundary or empty value. Explain what changed and why, rather than only copying the output.