Nov 03, 2013; 09:06
Sean Stephens
[$1000 Lasso Rosetta Contest] *Rules Update*
Rosetta Stoners
It would appear that it may or may not be fair to include LassoSoft employees in the RosettaCode.org contest. Although none of them knew about the contest any earlier than anyone else, nor have they used any special documentation or code available to anyone else (LassoGuide was last updated on Nov 1st, by parties who haven't posted examples yet) - I can appreciate that it may be construed that they have an unfair advantage.
Allow me to point out that this is specifically Jono - who is one of the most prolific and competent developers I have ever met. Once he is in the zone, I agree - it's pretty much unfair to try and compete with him. I certainly didn't ask he and his family to upend themselves from their home in New Zealand and move to Canada because of the balmy weather. He often goes overlooked in our community given that he is part of our team - but let's be clear: he's a programming superstar. The sport of Lasso is lucky to have him.
It reminds me of Wayne Gretzy;
"Wayne was so good that you could have a boy of your own who was a tremendous hockey player, and he'd get overlooked because of what the Gretzky kid was doing." - https://en.wikipedia.org/wiki/Wayne_Gretzky
So, instead of the contest being renamed "Try to beat Jono", I'm adding a layer of fairness.
Should a LassoSoft (or Treefrog) employee win the contest, we will still award them $1000 - that is fair, even for work done to date. In addition, the next-best point-scoring non-employee will also win $1000. That way, we continue to achieve the goal of Lasso's much-needed visibility, without intentionally crippling individuals who are willing to put their free time into promoting Lasso while having fun coding: working directly for us or not.
And let me be clear: I will be very, very impressed if someone can beat Jono.
Secondly, in order to open up the game a little (again, making it more fair for everyone involved), I propose some additional point opportunities.
We'll give you an additional 4 points for each of the "Draft Programming Tasks" you complete (adding 106 more examples to the contest);
http://rosettacode.org/wiki/Category:Draft_Programming_Tasks
Additionally, we'll up the points for "secondary" examples of how to do things, from 2 points to 3 points. That way, you can add a secondary example to someone else's (As Perl-heads would say "there's more than one way to do it"), even if an example has already been added.
*You don't get points for adding your own secondary example. You can add one, but you don't get points for it. That makes the playing field a little more fair.
Also - given the request by the admins - let's give away points just for making sure we leave their site clean and professional - the best possible representation of Lasso code possible.
So the "updated" points system, in review;
5 points for a first entry in a Task
4 points for a first entry on a Draft Task
3 points for a secondary entry on a Task (or Draft Task)
2 points for cleaning or improving an existing Task Entry's code
1 point for cleaning up or administrating cleanliness on someone else's task (spacing, output, etc.)
*Ergo, the maximum points you can get per task is 5.
Any questions or clarification needed - let me know!
Sean Stephens
CEO
LassoSoft Inc.
http://www.lassosoft.com
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>
Nov 03, 2013; 15:50
jolle
Re: [$1000 Lasso Rosetta Contest] *Rules Update*
Nov 03, 2013; 10:26
Sean Stephens
Re: [$1000 Lasso Rosetta Contest] *Rules Update*