How to Fix Errors Quickly

David Cramer of Sentry

David Cramer tells us how to catch and fix critical errors that can affect your bottom line. We also discuss the key differences between exceptions and bugs, and how to handle errors gracefully.

  • Here's what to listen for:
  • 00:43 What is an exception?
  • 01:21 What’s the difference between an exception and a bug?
  • 01:56 What might a developer do to cause an exception?
  • 02:30 What is the user’s experience when an exception occurs?
  • 04:32 Do exceptions mean developers aren’t writing code well?
  • 05:40 How can I become aware of the smaller errors that happen?
  • 11:38 Why are logs bad?
  • 12:49 If I can’t sift through logs as a developer, how is Sentry able to sift through it?
  • 13:51 What information do you need to fix an error?
  • 15:52 How do we reproduce bugs?
  • 17:44 Is it possible to use information from bugs to improve automated tests?
  • 18:43 What are my next steps after being notified about an error?
  • 20:19 What are the other side effects you might see from errors?
  • 24:16 Why is it not possible for Sentry to catch bugs?
  • 26:05 What can we do to minimize the chance of exceptions occurring?
  • 28:16 Are there any common things people should test for around exceptions?
  • 30:06 Why do you think people don't do automated testing?
  • 34:21 Are there any best practices on how to handle error display?
  • 36:40 How does Sentry use Sentry to monitor Sentry?

"A good example of a bug is maybe this page was supposed to be blue instead of red."

"An exception would be taking a one and dividing by zero, so the program would crash at that point."

"Users see bugs and those bugs may not result in an actual error, whereas an exception is a hard error."

"The main reason logs are bad is because I as a developer am never going to look at them."

"There’s a ton of data and you don’t really know what’s important. Is that error affecting the most people?"

"You throw that input into a test, you put the expected output (the error), and you just go fix the code."

"How does it affect the bottom line? Either it’s a monetary value or it’s overall customer happiness."

"More often the errors you’re seeing are machine to machine, so the customer would never even report those."

"Some software seems less buggy because they’ve been allowed to spend a lot of time focusing on tests."

"Sentry affords you the ability to take a little bit of risk because I’ll know about problems right away."

"Try not to joke about things. Have a page to apologize and be clear that there was an error that happened."

"If the error’s not in Sentry we probably don’t know about it."