What do you do when you need figure out what’s going on inside a gem, or just get a feel for its API?

I don’t use generated documentation to help me solve problems — often the library’s author and I disagree about what’s important to mention, and/or the documentation is fairly non-existent. Hey, I can’t whine… this stuff is free.

While I don’t necessarily agree with my esteemed colleague Adam Keys on his hypothesis that comments are a bad smell, I can definitely state that many smell bad. The fact they get generated into a prettier format also doesn’t help much… and well, we all know how often User’s Manuals and the like get updated.

Just get me to the code already!

Here’s a little script

Update 2008-12-23: Just use the gemedit gem :-)