[dlisboa]

Most people don't know all the tools at their disposal, or how to use them. I certainly don't and I consider myself above average in this regard.

Chrome DevTools has that issue since it's always changing, adding new things, and they're not discoverable/learnable from inside of it.

If you had a drawer of 50 kitchen implements, would you even think to search for the mandoline slicer if you didn't already know about it?

[nuancebydefault]

You are right. But what I wanted to say is, some people stick to very basic tools, even after you show them more convenient tools like a sharp knife with a firm handle and a knife sharpener. Often the switching part of the process seems to big of a hassle.

[shortrounddev2]

Yeah, I've shown the junior devs a dozen times how to set up breakpoints in VSCode and they still opt to console.log everything instead

[MonaroVXR]

I'm junior myself and this is so weird.

[sa46]

Chrome dev tools are an engineering marvel; the downside is it’s quite hard to find the perfectly shaped tool.

I spent about a week tracking down a memory leak in our web app. About 5 days in I discovered you could compare heap snapshots which led to the root cause of a chrome bug with hidden classes. The fix was to move object spread to the bottom of an object literal.

Here’s the bug. It was a fun one to hunt: https://crbug.com/v8/13303