-
Jim Weirich 4.24
Description:
You are happily writing new code for your system when all of a sudden the code is not behaving the way you thought it should. Perhaps you just created a failing test, and the code you wrote was expected to make the test pass ... but it doesn't. What's the first thing you do?
Some Rubyists will drop some "puts" statements into the code. Some will add a raise statement. And still others will depend on logging to trace the internals of the code. But a surprisingly few Rubyists will reach for the Ruby debugger.
Despite a general disdain for the debugger in the Ruby community, the Ruby debugger is a powerful tool that can quickly get to the heart of a coding problem. This talk will concentrate on getting Rubyists up to speed on the debugger, how to use it effectively and learning other general debugging tips.
Links: Website
Comments on this Talk
Mike,
02 Sep 01:06 AM
Thanks for pry
Jeff Casimir,
08 Sep 01:10 AM
Where do I take points off for subjecting us to Emacs....?
I kid, I kid!
Last Five Ratings
-
Jeff Casimir 4.54
-
Andrew Vida
-
delbert
-
Ryan McGeary
4.29
-
RandomGuy

I liked the real world examples, where we could actually see some code and also see the output of the commands. It was the only presentation where we actually got to see someone working on the command prompt.