Debugging Block

[mikeal]

Being that talks are only 20 minutes it would be a good idea to get an understanding of what each speaker is talking about so that we can order the talks in such a way that we can limit overlap and let the talks build on each other a bit.

@raynos @max123 @dshaw what are you thinking? I bet Max is talking about dtrace :)

[dshaw]

s/@rvagg/@raynos

[mikeal]

bah, yes, typing too fast :)

[max123]

Yes, I'll talk about DTrace. Not sure what exactly I'll talk about. 20 minutes, eh?

max

On Aug 1, 2013, at 8:50 AM, Mikeal Rogers notifications@github.com wrote:

Being that talks are only 20 minutes it would be a good idea to get an understanding of what each speaker is talking about so that we can order the talks in such a way that we can limit overlap and let the talks build on each other a bit.

@rvagg @max123 @dshaw what are you thinking? I bet Max is talking about dtrace :)

— Reply to this email directly or view it on GitHub.

[mikeal]

There are pretty long and open evenings that we're using for hacktime and some hands-on sessions. If you'd like us to set something up, or just keep a room open for "going deep" your talk could be more like a "this is DTrace and why you should care" lead-in to a deeper thing at night. We have a lot of space and a lot of time in the later parts of each day.

[dshaw]

If I'm going to stick to the topic, I'm probably going to share some techniques for debugging and reproducing errors, especially under load, on realtime systems.

[Raynos]

@dshaw I'm thinking about it. Either talk about "using joyent & smartos for debugging production shit". I have some exposure to mdb & smartos or cop out and talk about error handling using domains which is kind of debugging.

I mentioned that in the wrong issue.

[max123]

I'm planning on talking about debugging. I haven' t decided about exact topic, but shall include mdb. Workshops before and after will include debugging.

Sent from my iPhone

On Aug 13, 2013, at 16:42, Raynos notifications@github.com wrote:

@dshaw I'm thinking about it. Either talk about "using joyent & smartos for debugging production shit". I have some exposure to mdb & smartos or cop out and talk about error handling using domains which is kind of debugging.

I mentioned that in the wrong issue.

— Reply to this email directly or view it on GitHub.

[dshaw]

@Raynos @max123 Seems like it might be good to jump on a quick Skype or Hangout. I'd like to propose the following format:

1. @dshaw - debugging style for fun and profit (simple tools and approaches to make debugging saner. Differ mdb/dtrace et al to subsequent talks)
2. @Raynos - Next level: mdb, but not dtrace
3. @max123 - Final level: dtrace

That seems sane to me. What do you guys think?

[max123]

I plan on talking about both mdb and DTrace by going through a simple example app that crashes. Talking on skype works for me. I'm max.bruning on skype. Rgds Max

Sent from my iPhone

On Sep 4, 2013, at 15:20, Daniel Shaw notifications@github.com wrote:

@Raynos @max123 Seems like it might be good to jump on a quick Skype or Hangout. I'd like to propose the following format:

@dshaw - debugging style for fun and profit (simple tools and approaches to make debugging saner. Differ mdb/dtrace et al to subsequent talks) @Raynos - Next level: mdb, but not dtrace @max123 - Final level: dtrace That seems sane to me. What do you guys think?

— Reply to this email directly or view it on GitHub.

[Raynos]

@dshaw I was planning to focus on errors / domains instead of mdb. Can jump on skype.

[dshaw]

Debugging Style for Fun and Profit:

• Making logging sane.
• Logs and log aggregation in distributed systems.
• (I'd love to touch on Bunyan AKA, logging in JSON if that doesn't conflict with @max123.)
• REPL power tools
  • replify
  • repl-client (rc)
  • replpad
• Maybe continuation-local-storage, but that probably goes too far into what @Raynos will discuss.

I'll add you two to my talk repo once it goes up.

[Raynos]

@dshaw continuation-local-storage with a focus on tracing / logging doesn't go to far into my stuff.

continuation-local-storage with a focus on "roll your own error handling domains" would have overlap but we can just sync up on it.

[dshaw]

@Raynos I can deal with that delineation! Great.

[max123]

Looks good. Good luck fitting in 20 minutes. I won't go into bunyan

Sent from my iPhone

On Sep 4, 2013, at 16:19, Daniel Shaw notifications@github.com wrote:

Debugging Style for Fun and Profit:

Making logging sane. Logs and log aggregation in distributed systems. (I'd love to touch on Bunyan AKA, logging in JSON if that doesn't conflict with @max123.) REPL power tools replify repl-client (rc) replpad Maybe continuation-local-storage, but that probably goes too far into what @Raynos will discuss. I'll add you two to my talk repo once it goes up.

— Reply to this email directly or view it on GitHub.

[dshaw]

:-) @max123 @Raynos Thank you.

[Raynos]

@dshaw @max123 I have a draft of my slides up ( http://raynos.github.io/nodeconfeu/ )

maybe sync up in person if we want to make the transitions smoother

[juliangruber]

@Raynos: typo on slide 10 (your / you're)

[Raynos]

@juliangruber thanks! I fixed that.