# OT: Drifting off topic to debugger utility

**URL:** <https://www.ruby-forum.com/t/ot-drifting-off-topic-to-debugger-utility/58145>\
**Category:** Ruby\
**Created:** [April 18, 2006, 10:42pm UTC](https://www.ruby-forum.com/t/ot-drifting-off-topic-to-debugger-utility/58145 "2006-04-18T22:42:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickharlan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/77aa72/32.png) [@patrickharlan](https://www.ruby-forum.com/u/patrickharlan)\
**Post date:** [April 18, 2006, 10:42pm UTC](https://www.ruby-forum.com/t/ot-drifting-off-topic-to-debugger-utility/58145/1 "2006-04-18T22:42:26Z")

</div>

On 4/18/06, M. Edward (Ed) Borasky [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > James M. wrote:
> > 
> > >
> 
> [http://linuxcapacityplanning.com](http://linuxcapacityplanning.com)

I will vote in on the rarely use a debugger camp. The single exception  
(and this is rarely the case in Ruby :-), is when I have to figure out  
someone slse’s code and it does not have good unit tests and/or  
logging. Then being able to spelunk around in a good debugger is very  
useful (especially if it is _not_ multi-threaded).

pth