title: Is it bad practice to catch RuntimeException for logging purposes?
body: <p>I've come across the fact that catching RuntimeException is generally considered bad practice because they can't be corrected and usually are programmer errors.</p>
  
  <p>However, we have an (insanely) large application where changes in any part can have unforeseen consequences <em>(Yes, this a problem in and of itself)</em>.</p>
  
  <p>Now the idea has come up to start catching and logging RuntimeExceptions at the application's top level so we can be more efficient in fixing such bleed issues as they come up.</p>
  
  <p>Like every good Java team, we have a lovely zealous Uncle Bob follower who is absolutely forbidding us from doing it.</p>
  
  <p>How bad is it really to do this? Are there really no cases in which this is okay or even recommended?</p>