[ruby-talk:12692] Re: On-line CodeFest: Seeking subjects for small Ruby research experiment

I'd like to do this, please.

Would pair programming be ok?  I'd like to trick Leo Scott into doing this with me.  

If pair programming isn't allowed for this experiment, I'd still like to do it.

	Wayne Conrad

On Thu, 15 March 2001, Robert Feldt wrote:

> 
> Hi,
> 
> I'm finishing a report on a Ruby tool I've developed. As one part of
> the evaluation of the tool I need a number of Ruby implementations of
> a class from one and the same specification. I cannot develop
> them myself since that would invalidate the experiment (I know too much
> about the goals of the experiment to be a "real-world"/realistic
> subject). So, I'm asking you to help me.
> 
> I hope that a couple of folks on the list have the interest and time to
> be part of this. If you are then mail me at [e-mail]. I
> will send you a small survey with questions on your Ruby and
> computer-related experience. When you've answered them (it'll take you
> max 5 minutes) I'll send you a description of the development task with
> some additional guidelines on how to submit your solution. You'll get a
> requirements document for a class. Your task is to implement the class
> in Ruby. The task is not very large and you'll probably finish it in
> 0.5-3 hours. And you can always opt out if you find you don't have the
> time to finish.
> 
> Please consider taking part even if you are relatively new to
> Ruby; this is not a competition in writing "optimal" or beautiful Ruby
> code and I need a range of different solutions. See this as a
> learning experience; I will summarize and publish all solutions (I will
> anonymize them so your solution cannot be traced back to you if you don't
> want to) so that you can compare "your" solution to one of the
> "experts" (so experts: please consider taking part even though you
> already have existing and fun Ruby projects to work on). What tricks have
> others used? etc.
> 
> Some benefits to you and the Ruby community by taking part in this
> experiment:
> 
>  * It'll be fun (see it as a small excersise in Ruby development which
>    is what you love, eh ;-)).
> 
>  * You'll support research on Ruby which may make Ruby more known in
>    the academic (and industrial?) area => evoke more interest in and
>    use of Ruby => lead to more books, better extensions more
>    Ruby-related knowledge etc. (Well, I cant promise this chain of
>    events but it might happen)
> 
>  * The results of the experiment will increase the quality and
>    credibility of the paper => more probable it can be published => more
>    likely the "word on Ruby will spread".
> 
>  * You'll be acknowledged in the paper if you want to (I'll leave your
>    name out if you want)
> 
>  * The resulting Ruby programs/solutions will be submitted back to the
>    Ruby community. I'll pack them up and submit to RAA as public domain
>    (or with any other license on your code if you want). I'll
>    summarize the techniques used in the solutions and what can be
>    learned from them.
> 
>  * The results will help improve a tool for Ruby development which
>    will be submitted to RAA. It might be useful to you.
> 
>  * If you need similar help from me some time I'll try to help you out.
> 
>  * and I'll buy you a beer next time we meet (maybe we can have a
>    gathering at the RubyConference.new(2001)?). (That convinced you
>    didn't it... ;-))
> 
> If you think this sounds interesting and have the time to do it
> then please mail me as soon as possible. If you're interested
> but not sure that you'll have the time then please mail me anyway;
> I'll send you the task and you can make a more informed
> decision. However I must ask you not to discuss the task with fellow
> rubyists while the experiment is going on.
> 
> Please consider taking part in this experiment; I really need your
> help and I think the community as a whole will benefit.
> 
> BTW, I'm seeking reviewers for the paper before I submit it for
> publication. If you're interested please mail me.
> 
> Best regards,
> 
> Robert Feldt
> [e-mail]
> 
> Ps. 
> 
> Q: Why dont I tell you more about the tool and the goals of the
> experiment?
> 
> A: Because it might invalidate the experiment. I will publish both the
> paper and any results from the experiment once it has been finished
> and written up. All will be revealed... ;-... ;-)