Request to join Diagnostics WG

[naugtur]

I trace my diagnostics experience back to 2013 when I leaked gigabytes of RAM in the browser and stumbled upon some memory leaks in V8. I did fix the leaks and I've been helping my colleagues debug their JavaScript ever since.

My first version of node was 0.8, at the time of the 0.10 release, so I switched to 0.10 a few days in. My day job is focused on building maintainable software with a team where I'm the only person with extensive Node.js experience.

I enjoy teaching and I'm organizing community meet-ups in my area. My focus in teaching is the gap where people are not beginners anymore, but not ready to discover everything for themselves. With topics like debugging memory leaks.

Things I hope to contribute to the WG:

• Make diagnostics accessible to less experienced developers.
• Create educational docs and tools around diagnostics.
• Bring new ideas into the mix.
• Diversity - and it's not about me being from Poland;
  • thanks to hanging out with less experienced developers I can represent their perspective,
  • while everyone around core seems to prefer callbacks because they don't work with people who get trapped in callback hell easily, I'm a supporter of promises and I know what the pain points of their users are.

Top of my agenda:

• Find a way to inspect and visualize the event loop queue. Useful for live debugging without stopping the program, even more useful for educational purposes.
• Write about new / newly available tools, create a single source of instructions for diagnosing Node.js programs
• Advocate for and prototype tools for debugging without stopping the program
• Find a way to report blocking function names without setup that beginners, the ones most likely to write blocking functions, can't easily do

Thanks!

[AndreasMadsen]

Find a way to inspect and visualize the event loop queue. Useful for live debugging without stopping the program, even more useful for educational purposes.

It is not a live debugging tool but you might be interested in dprof.

Write about new / newly available tools, create a single source of instructions for diagnosing Node.js programs

I'm very excited about this.

[watson]

I met @naugtur at NodeConf Budapest where he was really enthusiastic about joining this WG. I encouraged him to make this PR 😃