Podcast: Play in new window | Download (Duration: 1:01:30 — 70.4MB)
Panelists
- Charles Max Wood (twitter github Teach Me To Code)
- Peter Cooper (site twitter github The Ruby Show Ruby Inside)
- James Edward Gray II (blog twitter github)
- Gregory Brown (blog twitter github Ruby Mendicant University)
- Mike Moore (blog twitter github Rubiverse Podcast)
Items discussed in today’s episode
- Debuggers and Tools
- Ruby Debug
- pry
- Ruby in Steel
- other IDE’s
- Formatting Debug Output
- Outputting debug information
- Other debugging tricks
- abort_on_exception = true
- The Ruby executable’s -d switch and the $DEBUG constant
- Using a logger to output data from a specific piece of code
- The debug method in Rails helpers and views
- Using Object#freeze on to find what is modifying the object
- Passing a dummy object that uses method_missing to output method calls and arguments
- Do not debug alone
- Spike the debugging, git stash the changes, write the test, unstash the changes and verify the result
Panel Picks
- Gaming side events at conferences
- Lost Cities Board Game
(Affiliate Link)
- Jambo
(Affiliate Link)
- Pandemic
(Affiliate Link)
- Agricola
(Affiliate Link)
- Race For The Galaxy
(Affiliate Link)
- Ticket To Ride
(Affiliate Link)
- The Settlers of Catan
(Affiliate Link)
- Scrabble Crossword Game
(Affiliate Link)
- awesome_print
- rails footnotes
- go
- The Go Programming Language, or: Why all C-like languages except one suck.
- Mobile Magic (Disneyland Android App)
- Elantris
(Affiliate Link)
- iPad Kindle App
- Couch to 5k
- Rubyflow.com
- open_gem
{ 3 comments… read them below or add one }
Fun podcast as always guys.
That question on the open_gem pick at the end about how you don’t change an opened gem or how you revert changes is easy to answer.
A ‘gem i your_gem’ will revert any changes you make. It’s actually a method I ‘ve used often: Edit the gem files directly to add some debugging output or make some changes then rollback any changes with gem i.
open_gem is an awesome shortcut for this method, cheers.
V.-
Since you asked for extra debugging tips in the comments…
If you ever find yourself wondering where the sodding hell that damn method is defined, on 1.9.2 you can do “method(:my_method).source_location” and get the file and line number
Bundler can open up a gem in your editor as well: `bundle open name_of_gem`. Since I use Bundler for just about every project, I’ve gone this route as opposed to installing another gem.
{ 1 trackback }