Sign in Subscribe

I=['daddy']; I.concat(['gineer', 'trepreneur'].map(x => 'en'+x))

console.log(null || undefined || 0 || '?')

Debugging NiM

* Set "Developer mode" by checking the "Developer mode" checkbox at the chrome://extensions page * Now go to the NiM extension item on the same page (you may have to scroll down if you have lots of extensions installed) and you should now see the background.html

"F#!k off with your email & web traffic sniffing."

web traffic sniffing Featured

"F#!k off with your email & web traffic sniffing."

I've often heard that developers in the open source community can be a bit harsh, indeed just 3 days ago the host and guest one of my favorite podcasts [1] touched briefly on that sentiment. By the way, shouts outs to Jeff and Erika, your podcast is great,

Inspect Broke My Workflow!

Coding Featured

Inspect Broke My Workflow!

A few months ago I began using the built in Node V8 Inspector in lieu of node-inspector. My personal choice for switching came out of sticking to the path of least resistance, and for me, that entails keeping tooling as minimal as possible. Metaphorically speaking, the prospect of having one

NIM (Node Inspection Monitor)

NIM (Node Inspection Monitor)

What is it? A Chrome Extension that monitors the integrated Node V8 inspector and automates the management of Chrome DevTools during development using Node.js. Excerpts taken from various online forums: Is there a way to get chrome-devtools (--inspect) to automatically detach from a process that has ended?[1] How