Chrome developer tools to master

Post by pvg » Mon, Jul 09, 2018, 9:27 PM UTC

0xfeba wrote: post #30

judofyr wrote: post #14

Earlier quoted context omitted.

Can’t you just ask them if they have experience with the Chrome debugger? And if that’s such a deal breaker for you, you can teach them in the first week? I mean, it’s not like the Chrome debugger is such a complicated beast. Even if you have no experience with it, you can probably learn 90% of the useful tricks in a few hours.

I do. I just verify. They can also use Firefox or any other browser's tools if they are more comfortable. We are not hiring junior devs, and even if so I would still probably ask. But experienced front end devs should know how to use a browser's debugger. Like others said, it's a flag that they potentially don't have problem solving skills. I mean, if they put a single console.log near what they think is going wrong…

Post by homero » Mon, Jul 09, 2018, 9:30 PM UTC

Post by homero » Mon, Jul 09, 2018, 9:33 PM UTC

swaggyBoatswain wrote: post #42

Chrome developer tools is just a godsend. Its so much better than any other debugger I've worked with, and miles better than firefox debugging tool I personally use a chromium based browser called slimjet to do all of my development. It runs off v55 I think which is like 5 versions behind chrome. But its nice to have a dedicated app for debugging. One tool that I find I use everyday is this: http://lab.maltewasserman…

Post by kaycebasques » Mon, Jul 09, 2018, 9:44 PM UTC

codezero wrote: post #7

This is great, besides the Sources tab, I use DOM and Event breakpoints a ton to debug a lot of problems. Something, I'm not sure if most people know, if you break somewhere (whether event or DOM), you can access the currently in scope variables directly in the console. It's extremely useful for finding out what's going on with something in the middle of hairy code at a specific point in time.

Post by giancarlostoro » Mon, Jul 09, 2018, 9:46 PM UTC

sehugg wrote: post #44

0xfeba wrote: post #30

Earlier quoted context omitted.

I do. I just verify. They can also use Firefox or any other browser's tools if they are more comfortable. We are not hiring junior devs, and even if so I would still probably ask. But experienced front end devs should know how to use a browser's debugger. Like others said, it's a flag that they potentially don't have problem solving skills. I mean, if they put a single console.log near what they think is going wrong…

I've written debuggers, and I still use console.log quite often. I would be pretty annoyed if I were silently judged on my choice of debugging tool.