When to Use Try Catch

Being fault tolerant and catching errors is often an after thought when it comes to coding standards in businesses simply because we tend to think about how our software works, not how it breaks. We’ve all come across the “What were they thinking” code now and then, and I’ve started to notice a trend regarding unnecessary or improper Try Catching, and that is they show up most often from newer programmers or those experienced but unfamiliar or uncomfortable to a particular part of the codebase. While these are clearly not the right reasons to use Try Catch, I can’t recall ever seeing an official “When/Why to” article.