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.
"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."