[RAD stands for
Ruby Ape Diaries, of which
this is part IX.]
Ruby’s debugging facilities, compared to what IDE users like me are used to,
are, well... sincere.
At one point during the Ape work, I had a bug that was really driving me
crazy. The symptom was that my HTTP interaction with the server would just
freeze up, and I couldn’t spot the pattern behind it.
It’s a fact of protocol-testing life that this particular kind of shit happens.
Sometimes you’re reduced to debugging with print statements, and I was.
But after a while they weren’t helping me, I was calling
Net::HTTP#start on an apparently-valid connection and
Eventually, I was driven to looking in the library source,
net/http.rb. Hey, it was easy to understand! (Have I talked about
Ruby and readability before?) I could see where
my request was going, but I couldn’t see how it could go wrong. Well, this is
a dev machine, and Real Men debug with