It can be helpful when debugging to know what "super" is actually calling.
I've spent part of the last couple days debugging the bowels of a pesky Rails project. The issue was the infamous Stack Level Too Deep error.
I found the source of the problem was a gem's method calling
super. And while the stack trace of an error will show you the pathway of an error, sometimes it can be helpful to manually find that pathway yourself during the debugging process.
It can be done in a quick one-liner using the name of the method:
method_name is the name of the method you want to check.
Here's a simplistic example to demonstrate:
class B < A
a = A.new
a.foo # => bar
b = B.new
b.foo # => #<Method: A#foo>
Logging output during ruby processes is hugely beneficial for gaining insight into running code.
Command line scripts aren't so bad to write when you've got Ruby on your side.
A quick way to pull content from a URL and parse it using Ruby.