DEV Community

Discussion on: Don't Get Fooled By Errors

Collapse
 
ssimontis profile image
Scott Simontis

Also, crystal clear instructions for replication are the most valuable asset when fighting a nasty bug. Nothing is worse than the issues which magically go away whenever you call your coworker to come take a look at this. Also, see if you can isolate the code and still trigger the error - if you can extract part of your code into a smaller demo that triggers the error, it will be much easier to share with co-workers and vendors and decrease the surface area you must investigate.

I am also a fan of APM tools like Raygun or New Relic or elmah.io. Learning about errors from your users without them having to tell you is incredibly valuable, and many of these tools will look for correlations between errors to help you find the source and some can even predict how high of a priority the bug is in terms of lost customer interactions.