# Pair programming next week

**URL:** <https://www.ruby-forum.com/t/pair-programming-next-week/178151>\
**Category:** IronRuby\
**Created:** [October 29, 2009, 9:55pm UTC](https://www.ruby-forum.com/t/pair-programming-next-week/178151 "2009-10-29T21:55:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shri\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/898d66/32.png) [@Shri\_B](https://www.ruby-forum.com/u/Shri_B)\
**Post date:** [October 29, 2009, 9:55pm UTC](https://www.ruby-forum.com/t/pair-programming-next-week/178151/1 "2009-10-29T21:55:19Z")

</div>

The last few pair programming sessions had worked out very well. Since  
its been a while since we did one, I want to find out if anyone is  
interested in doing in again next week. Reply (just to me) if you have  
an IronRuby-task (some suggestions at  
[http://wiki.github.com/ironruby/ironruby/contributing](http://wiki.github.com/ironruby/ironruby/contributing)) that you would  
like help with. Once I know who all are interested, we can work out a  
time that works for everyone.

Here is the info from [http://wiki.github.com/ironruby/ironruby/debugging](http://wiki.github.com/ironruby/ironruby/debugging)  
:  
Pair debugging with experienced IronRuby developers

Some experienced IronRuby developers may be available to debug a problem  
with you. Watching over their shoulder can help a newcomer to the code  
base learn debugging tips and techniques. To make this a fruitful  
exercise, please follow the following guidelines:

- Send email to  
removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) asking  
if any experienced developer is available to help you
- Ensure that you can build and successfully run all of the  
RubySpec[http://wiki.github.com/ironruby/ironruby/rubyspec](http://wiki.github.com/ironruby/ironruby/rubyspec) tests.
- Restrict the problems to pure Ruby code which is known to work  
with MRI. Ensuring a clean working baseline functionality in MRI ensures  
that the problem truly in IronRuby. Without a known clean MRI baseline,  
the problem can be in a component other than IronRuby which you are as  
well-equipped to diagnose as anyone else.
- Set up a clean repro. Spend time ensuring that it is not a  
configuration issue, and that the problem can be easily reproduced on  
other machines. Document detailed information about your platform,  
version of IronRuby, and the steps to repro the problem.
- Do basic debugging by yourself beforehand. This will ensure that  
you get the most out of the session and can keep up with what’s going on  
over Live Meeting.
- Set up Live Meeting[http://livemeeting.com](http://livemeeting.com) on your machine, which  
will allow you to watch the debugging session.
- The Live Meeting invite will be sent by email just before the  
scheduled hour.
- The email invite will also contain a toll-free number to dial in  
to. If you cannot call in, add the experienced developer as a  
friend/buddy in some Chat program so that you can ask questions during  
the debugging session.