Brandon Dimcheff - Down The Rabbit Hole - Chasing bugs from the browser to the backend
JSConf US 201329 May 2013
When a bug occurs/is reported, there’s always these stages
- there’s no way this is happening (PEBKAC)
- listen to users
- How often is this problem happening?
- Graph things to see scope of problem
- unix: jsontool (npm install jsontool)
go back to logs find info
(log everything! more data = more chance of tracking issues down)
- how can you reproduce scenario in which error occurred?
- do the stupidest, easiest thing that works (no rabbit holes)
- chrome dev tools
“shotgun debugging” - breakpoints EVERYWHERE
- Graph everything
- log everything
- do stupidest, easiest thing that works rather than fancy solutions
- learn your tools
- listen to your users (no more denial!)
Brandon is from Olark - they’re hiring
This is a quick summary of a talk I attended at JSConf 2013. You can see a list of all those I've summarized notes from here. There's also a General thoughts during JSConf 2013 post for all the non-talk bits and pieces.
There were 3 concurrent tracks at the conference, so only those I attended myself are summarized here. Other attendees have summarized some of the talks I didn't get to due to scheduling conflicts - you can find those at jlongster.com (James Long) and Toby Ho's github repo.