JavaScript Error Tracking with {Track:js}

736 views
590 views

Published on

The web today is far more than your server stack! Content is combined with a rich interactive layer of JavaScript and mashed up with external social, advertising, or service providers. All this into a rapidly changing environment of new browsers, new rendering engines, new libraries, and new plugins.

My founders and I at {Track:js} believe that JavaScript can and should be better--we should know about our errors--and we should fix them! It's our mission to give you the tools to do this.

Let's talk about why you should care about your clientside errors, and how to build a basic implementation. Then I'd like to show you how {Track:js} can accelerate it, improving quality, and giving you more context about your errors than you thought possible!

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
736
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

JavaScript Error Tracking with {Track:js}

  1. 1. {Track:js} Todd H Gardner @toddhgardner
  2. 2. {Track:js} 1. Why 2. How JavaScript Error Logging
  3. 3. Your Server
  4. 4. We have great tools to track this
  5. 5. http://www.flickr.com/photos/mark_i_geo/ Customer Reflection
  6. 6. Why don’t we track this?
  7. 7. defect free JavaScript? tell me another one
  8. 8. you depend on the cloud how do you know when it’s storming?
  9. 9. the web is changing fast how do you handle the unexpected?
  10. 10. {Track:js} 1. Why 2. How JavaScript Error Logging
  11. 11. Console API
  12. 12. http://www.flickr.com/photos/lucy_hill/ if an error falls in a browser does anyone hear it?
  13. 13. http://www.flickr.com/photos/lucy_hill/ what’s the context of the crime
  14. 14. Try-Catch Yoda was wrong! http://www.flickr.com/photos/51025521@N04/ we must try and catch
  15. 15. {Track:js} 1. Why 2. How JavaScript Error Logging
  16. 16. {Track:js}
  17. 17. {Track:js}
  18. 18. trackjs.com {Track:js} todd@trackjs.com @toddhgardner github.com/TrackJs/Tech-Demo

×