search

lnug / speakers

Open an issue to submit a talk
https://github.com/lnug/speakers
43 stars 7 forks source link

Debugging Node.JS #66

Closed srounce closed 8 years ago

srounce commented 8 years ago

"What's a debugger?", "What's the *point of debugging?", *"How do I debug Node?", "But what about TDD?", and _"Why the ƒ#@|{ doesn't my code run?"_. Life's great questions. Join me, as we peel back the layers of preconceived debugging drudgery, to reveal the answers to these questions — and some others you never asked.

admataz commented 8 years ago

Thanks @srounce

We'll need a bit more info about your talk...

You can refer to previous speakers' proposals for some idea: https://github.com/lnug/speakers/issues?q=is%3Aissue+is%3Aclosed+label%3A%22Accepted+%26+Scheduled%22

Thanks!

jkbits1 commented 8 years ago

Hi,

this talk relates to conversations with @srounce at the recent Nodeschool London.

There are a few tools for debugging node in the chrome devtools environment. How they relate to, and use, V8 can affect their efficiency.

It would be great to have a talk (maybe somewhere between lightning and full-length) on how these tools work, and which one is more efficient and why.

I'm particularly keen to hear this talk.

srounce commented 8 years ago

Basically I saw the talk going something like this:

  1. Introduce the problem
    • How do I know what’s gone wrong?
    • How a the term 'bug' came about and how it kinda still holds true in a funny kinda way (tenuous, maybe not)
  2. Naive techniques
    • console.*
    • throwing errors etc.
  3. Node cli debugger
    • It’s usable but still a little bit of a pain
  4. Devtools!
    • Ah but what about node?
  5. Node inspector
    • This is more like it!
    • Still kinda slow ( :/ )
  6. Bugger
    • Node’s delegation of debugging to the V8 debugger protocol
    • summarize nodejs/node#2546 for the tl;dr'ers
  7. Future
    • Literate programming tools (lambdu)
    • real-time coverage (brackets, theseus, etc)
    • any other cool (and useful!) early days projects I find before the time
jkbits1 commented 8 years ago

@srounce this is definitely an excellent talk :+1:

I use node-inspector a lot, and it goes from being responsive to being really dragging then back again. If only to understand the underlying mechanisms more deeply, I'm keen to hear about this project https://github.com/buggerjs/bugger

iancrowther commented 8 years ago

@srounce can you update "Blah blah blah I need to do a talk in" to be a condensed description that we can use on the website/newsletter.

jkbits1 commented 8 years ago

@srounce the reason for Ian's comment is that the web site automates adding the talk descriptions. It take the first comment of the issue and put's it straight onto the page. If you look at some closed issues you'll see a bunch of examples.

iancrowther commented 8 years ago

@srounce how soon can this talk be ready? We currently have an open slot next week! if not April?

iancrowther commented 8 years ago

@srounce can you do this talk in April?

srounce commented 8 years ago

Hi, sorry for the slow comms, I've been totally snowed with work punctuated by sporadic intervals of being bedridden with flu. I've been dragging this on now I know, but I'm not 100% sure I'm going to be able to make it this month (we've got some hefty pitches lined up over the next couple of weeks). Shall we say May and I'll treat it like a deadline from now on? Are you around the weekend of the 6/7th for a run through and crits?

jkbits1 commented 8 years ago

@srounce I've had a virus dragging on too, it's a real pain ! I could be around that weekend. Interested to see how the https://github.com/buggerjs/bugger project is going

iancrowther commented 8 years ago

@srounce right I just added May 25th as the milestone, pls confirm

admataz commented 8 years ago

Hey @srounce - hope you're holding up! I'd love to confirm May's lineup before this Wednesday's meetup... can you confirm?

srounce commented 8 years ago

Confirmed for May.

@jkbits1 @iancrowther Are either of your guys still around this weekend, to go thru what I've managed to get together so far?

admataz commented 8 years ago

Thanks @srounce - you are scheduled and confirmed for May

jkbits1 commented 8 years ago

@srounce I'm not around this weekend, next weekend is possible

srounce commented 8 years ago

Yep that sounds cool, you've got my number or shall I PM you on gitter?

On Wed, 27 Apr 2016, 15:04 Jon Kelly, notifications@github.com wrote:

@srounce https://github.com/srounce I'm not around this weekend, next weekend is possible

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/lnug/speakers/issues/66#issuecomment-215093672

clarkie commented 8 years ago

@srounce Any chance you could update the description in this issue so that we can display a bit more information on the website: http://lnug.org

Thanks

jkbits1 commented 8 years ago

@srounce this weekend is good for me

admataz commented 8 years ago

Hey @srounce - great to meet you at nodeconf the other day. I've updated the opening comment in this issue so it can be pulled into the website and I can use it for the newsletter - can you check/confirm it's alright for you? Thanks!

srounce commented 8 years ago

Hey @admataz just updated OP, can you confirm that it's legit for publication?

jkbits1 commented 8 years ago

@srounce @admataz Sounds great!

admataz commented 8 years ago

@srounce - all good! much better than what I had written