Over the past year, I’ve been touring software conferences and sharing some techniques for finding and debugging some of the most common errors on the web with a talk I call “JavaScript Forensics”. JSConfEU did a marvelous job recording and producing the talk, and I’d like to share it with you all. I hope you like it.
Something terrible has happened. Errors litter the floor; memory leaking from cracks in the ceiling. Someone lost their object context in the corner. Everything reeks of jank. The web is overrun. In this session, a JavaScript error tracking expert tracks down some of the most common and most dangerous outlaws of web applications. You’ll leave the session armed with track down and capture the problems in your own JavaScript web applications. Bring your bugs and let’s fix up our web.
Resources
This talk represents years of experience helping developers track down and fix JavaScript errors in production applications. The techniques shared here come directly from real-world debugging scenarios we’ve encountered while building and improving TrackJS.
If you’re dealing with JavaScript errors in your own applications and want to put some of these forensic techniques to work, give TrackJS a try and see how better error monitoring can help you debug faster and build more reliable applications.
