Talking Code

How to Fix Errors Quickly

Episode Summary

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.

Episode Notes

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?