Comments on: Debugging your Ruby Programs

By: Peter Schröder (@phoet)

Peter Schröder (@phoet) — Mon, 20 Jul 2015 18:52:06 +0000

thanks for the article, for those that want to read more on the topic i'd like to link to one of my articles about debugging rails applications in development: http://nofail.de/2013/10/debugging-rails-applications-in-development/

By: John Denisov

John Denisov — Sat, 18 Jul 2015 07:23:15 +0000

Knowing about curl is good thing. But using it for everyday debugging is cumbersome. There are plenty of great tools like postman(https://www.getpostman.com/features) for debugging http requests/responses. Although browser-based solutions can’t modify headers blocked by browser like Origin

By: dariodaic

dariodaic — Sat, 18 Jul 2015 03:26:05 +0000

Using p(obj) instead of puts(obj.inspect) is not preferable just because of brevity. If need be, #inspect can be overridden. The idea is to dump the object itself, e.g. String#inspect wraps an object in quotes (like so – “self”). It can be very useful on instances of your own classes if you get stuck.

Excellent choice of the subject! Loved the tip for “require pry” snippet.

By: admin

admin — Wed, 15 Jul 2015 01:15:16 +0000

Thanks for your comment! I agree, pry-byebug is great

By: abargnesi (@abargnesi)

abargnesi (@abargnesi) — Wed, 15 Jul 2015 00:59:24 +0000

Good post, thanks for introducing me to sysdig.

One note on byebug:

You can use David Rodríguez’s pry-byebug gem (https://github.com/deivid-rodriguez/pry-byebug) to use the byebug commands within the pry repl. Now you will have syntax highlighting + byebug’s powerful debugging capabilities.