It’s almost 2020 and yet… Checked Exceptions are still a thing

In theory, there is no difference between theory and practice. In practice, there is.

  • Exposing Implementation Details in the Signature
  • No Appropriate Handling Possible (In some cases)
  • No Recovery Possible (In some cases)
  • Java 8 Lambdas and Streams
  • Always catch all checked exceptions at source and rethrow them as LogRuntimeException.
  • All of my methods do not declare any exceptions
  • As I discover that I need to deal with a specific exception I go back to the source where LogRuntimeException was thrown and I change it to <Specific>RuntimeException (This is rarer than you think)
  • Net effect is that when you come across a try-catch clause you better pay attention as interesting things are happening there.




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Outsystems Next Step 2017

Embracing NewSQL: Why We Chose TiDB over MongoDB and MySQL

8 Non-exhaustive List of What You Can Do in Python

Drawback of Numpy over list: When you should not use Numpy ?

FHIR for Developers: Part 2

Loops in Python | Using Jupyter Notebook (Python for Data Science)

App Engine to Google Kubernetes Engine — a journey

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


More from Medium


Java, JVM, JRE and JDK

Numbers and statics

Java Newsletter — Issue 12