<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Lessons Learned from July Contest</title>
	<atom:link href="http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/</link>
	<description>Practice. Compete. Discuss.</description>
	<lastBuildDate>Sun, 12 Feb 2012 15:11:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Rahul</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-280</link>
		<dc:creator>Rahul</dc:creator>
		<pubDate>Fri, 25 Sep 2009 13:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-280</guid>
		<description>Chef : The contest needs to be shorter.  Next month’s contest will be one week long.  We will also be including a shorter duration contest at the end of next month (a few hours to a weekend - still deciding).&lt;br&gt;&lt;br&gt;Rahul : Well , honestly I wouldn&#039;t want the contest to be shorter for I am a novice and I found the longer duration of the competition to be an advantage for me , not just in getting my submissions accepted but in improving my algorithmic skills as well . My general scenario was reading the problem statement and then making a brute force solution thus getting TLE , then trying to optimize it and still get another TLE . Then however I would search Google for new and better algorithms and try to implement them and keep on doing this until I get a solution accepted . During the June Algorithm Challenge , I had to submit nearly 50 submissions per problem to get my solution accepted and at least 10 of them had different strategies and various had different types of optimizations thus explaining and answering some of my questions as to which solutions are better and why . Most of my time during June Algorithm Challenge , in fact all of it , was gone into thinking about &quot;Why did that Algorithm gave an TLE &quot; and thus learning about new algorithms . Even after the contest , most of my time was spent in learning new algorithms , strategies etc and solving problems at other judges like UVa and I am able to see some improvement in me . No more of my programs are getting TLEs at other judges now . So I would really really wish for a longer contest .</description>
		<content:encoded><![CDATA[<p>Chef : The contest needs to be shorter.  Next month’s contest will be one week long.  We will also be including a shorter duration contest at the end of next month (a few hours to a weekend &#8211; still deciding).</p>
<p>Rahul : Well , honestly I wouldn&#39;t want the contest to be shorter for I am a novice and I found the longer duration of the competition to be an advantage for me , not just in getting my submissions accepted but in improving my algorithmic skills as well . My general scenario was reading the problem statement and then making a brute force solution thus getting TLE , then trying to optimize it and still get another TLE . Then however I would search Google for new and better algorithms and try to implement them and keep on doing this until I get a solution accepted . During the June Algorithm Challenge , I had to submit nearly 50 submissions per problem to get my solution accepted and at least 10 of them had different strategies and various had different types of optimizations thus explaining and answering some of my questions as to which solutions are better and why . Most of my time during June Algorithm Challenge , in fact all of it , was gone into thinking about &#8220;Why did that Algorithm gave an TLE &#8221; and thus learning about new algorithms . Even after the contest , most of my time was spent in learning new algorithms , strategies etc and solving problems at other judges like UVa and I am able to see some improvement in me . No more of my programs are getting TLEs at other judges now . So I would really really wish for a longer contest .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahul</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-1686</link>
		<dc:creator>Rahul</dc:creator>
		<pubDate>Fri, 25 Sep 2009 13:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-1686</guid>
		<description>Chef : The contest needs to be shorter.  Next month’s contest will be one week long.  We will also be including a shorter duration contest at the end of next month (a few hours to a weekend - still deciding).Rahul : Well , honestly I wouldn&#039;t want the contest to be shorter for I am a novice and I found the longer duration of the competition to be an advantage for me , not just in getting my submissions accepted but in improving my algorithmic skills as well . My general scenario was reading the problem statement and then making a brute force solution thus getting TLE , then trying to optimize it and still get another TLE . Then however I would search Google for new and better algorithms and try to implement them and keep on doing this until I get a solution accepted . During the June Algorithm Challenge , I had to submit nearly 50 submissions per problem to get my solution accepted and at least 10 of them had different strategies and various had different types of optimizations thus explaining and answering some of my questions as to which solutions are better and why . Most of my time during June Algorithm Challenge , in fact all of it , was gone into thinking about &quot;Why did that Algorithm gave an TLE &quot; and thus learning about new algorithms . Even after the contest , most of my time was spent in learning new algorithms , strategies etc and solving problems at other judges like UVa and I am able to see some improvement in me . No more of my programs are getting TLEs at other judges now . So I would really really wish for a longer contest .</description>
		<content:encoded><![CDATA[<p>Chef : The contest needs to be shorter.  Next month’s contest will be one week long.  We will also be including a shorter duration contest at the end of next month (a few hours to a weekend &#8211; still deciding).Rahul : Well , honestly I wouldn&#039;t want the contest to be shorter for I am a novice and I found the longer duration of the competition to be an advantage for me , not just in getting my submissions accepted but in improving my algorithmic skills as well . My general scenario was reading the problem statement and then making a brute force solution thus getting TLE , then trying to optimize it and still get another TLE . Then however I would search Google for new and better algorithms and try to implement them and keep on doing this until I get a solution accepted . During the June Algorithm Challenge , I had to submit nearly 50 submissions per problem to get my solution accepted and at least 10 of them had different strategies and various had different types of optimizations thus explaining and answering some of my questions as to which solutions are better and why . Most of my time during June Algorithm Challenge , in fact all of it , was gone into thinking about &#8220;Why did that Algorithm gave an TLE &#8221; and thus learning about new algorithms . Even after the contest , most of my time was spent in learning new algorithms , strategies etc and solving problems at other judges like UVa and I am able to see some improvement in me . No more of my programs are getting TLEs at other judges now . So I would really really wish for a longer contest .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Merriman</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-279</link>
		<dc:creator>Stephen Merriman</dc:creator>
		<pubDate>Tue, 21 Jul 2009 11:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-279</guid>
		<description>My thoughts:

a) I&#039;m happy with a week long contest. While there was room for optimisation on the challenge problem, I basically solved the rest of the problems in the first few days, played around with the challenge for a while, and then just sat back and waited, knowing a heap of people would end up solving the problems and it would come down to who felt like spending the most time playing with minor optimisations for the challenge problem. 32 people solving all problems was probably a bit too high.

b) Another contest in the month is excellent, but whatever you do, PLEASE don&#039;t make it less than 24 hours long - make it a multiple of 24 hours. A worldwide contest is ruined otherwise; I have to put up with the fact that most online contests are in the middle of my night, but I don&#039;t want this to happen to Codechef. Please keep it a true worldwide contest, rather than just for people who are lucky to have it suit their timezone.

c) I agree that forum posts need to be checked more regularly. The description of the challenge problem was completely wrong for the majority of the contest, and I&#039;m sure lead to many people getting frustrated with the fact that any optimisations gave them a worse score.

And finally, d) While this may not be possible with the current online judge system, how about something like this to make challenge problems work better. Provide two sets of test cases; one which works like currently with unlimited submissions, and one, which is used in the final scores, with limited submissions per day which doesn&#039;t display the results for a day (or something similar). That way you can still play with your solution on the first set, still be able to make sure the real case will work fine on your code, yet prevent the reverse engineering or mass submissions issues.

e) It was still a great contest :)</description>
		<content:encoded><![CDATA[<p>My thoughts:</p>
<p>a) I&#8217;m happy with a week long contest. While there was room for optimisation on the challenge problem, I basically solved the rest of the problems in the first few days, played around with the challenge for a while, and then just sat back and waited, knowing a heap of people would end up solving the problems and it would come down to who felt like spending the most time playing with minor optimisations for the challenge problem. 32 people solving all problems was probably a bit too high.</p>
<p>b) Another contest in the month is excellent, but whatever you do, PLEASE don&#8217;t make it less than 24 hours long &#8211; make it a multiple of 24 hours. A worldwide contest is ruined otherwise; I have to put up with the fact that most online contests are in the middle of my night, but I don&#8217;t want this to happen to Codechef. Please keep it a true worldwide contest, rather than just for people who are lucky to have it suit their timezone.</p>
<p>c) I agree that forum posts need to be checked more regularly. The description of the challenge problem was completely wrong for the majority of the contest, and I&#8217;m sure lead to many people getting frustrated with the fact that any optimisations gave them a worse score.</p>
<p>And finally, d) While this may not be possible with the current online judge system, how about something like this to make challenge problems work better. Provide two sets of test cases; one which works like currently with unlimited submissions, and one, which is used in the final scores, with limited submissions per day which doesn&#8217;t display the results for a day (or something similar). That way you can still play with your solution on the first set, still be able to make sure the real case will work fine on your code, yet prevent the reverse engineering or mass submissions issues.</p>
<p>e) It was still a great contest <img src='http://blog.codechef.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Merriman</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-1685</link>
		<dc:creator>Stephen Merriman</dc:creator>
		<pubDate>Tue, 21 Jul 2009 11:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-1685</guid>
		<description>My thoughts:

a) I&#039;m happy with a week long contest. While there was room for optimisation on the challenge problem, I basically solved the rest of the problems in the first few days, played around with the challenge for a while, and then just sat back and waited, knowing a heap of people would end up solving the problems and it would come down to who felt like spending the most time playing with minor optimisations for the challenge problem. 32 people solving all problems was probably a bit too high.

b) Another contest in the month is excellent, but whatever you do, PLEASE don&#039;t make it less than 24 hours long - make it a multiple of 24 hours. A worldwide contest is ruined otherwise; I have to put up with the fact that most online contests are in the middle of my night, but I don&#039;t want this to happen to Codechef. Please keep it a true worldwide contest, rather than just for people who are lucky to have it suit their timezone.

c) I agree that forum posts need to be checked more regularly. The description of the challenge problem was completely wrong for the majority of the contest, and I&#039;m sure lead to many people getting frustrated with the fact that any optimisations gave them a worse score.

And finally, d) While this may not be possible with the current online judge system, how about something like this to make challenge problems work better. Provide two sets of test cases; one which works like currently with unlimited submissions, and one, which is used in the final scores, with limited submissions per day which doesn&#039;t display the results for a day (or something similar). That way you can still play with your solution on the first set, still be able to make sure the real case will work fine on your code, yet prevent the reverse engineering or mass submissions issues.

e) It was still a great contest :)</description>
		<content:encoded><![CDATA[<p>My thoughts:</p>
<p>a) I&#8217;m happy with a week long contest. While there was room for optimisation on the challenge problem, I basically solved the rest of the problems in the first few days, played around with the challenge for a while, and then just sat back and waited, knowing a heap of people would end up solving the problems and it would come down to who felt like spending the most time playing with minor optimisations for the challenge problem. 32 people solving all problems was probably a bit too high.</p>
<p>b) Another contest in the month is excellent, but whatever you do, PLEASE don&#8217;t make it less than 24 hours long &#8211; make it a multiple of 24 hours. A worldwide contest is ruined otherwise; I have to put up with the fact that most online contests are in the middle of my night, but I don&#8217;t want this to happen to Codechef. Please keep it a true worldwide contest, rather than just for people who are lucky to have it suit their timezone.</p>
<p>c) I agree that forum posts need to be checked more regularly. The description of the challenge problem was completely wrong for the majority of the contest, and I&#8217;m sure lead to many people getting frustrated with the fact that any optimisations gave them a worse score.</p>
<p>And finally, d) While this may not be possible with the current online judge system, how about something like this to make challenge problems work better. Provide two sets of test cases; one which works like currently with unlimited submissions, and one, which is used in the final scores, with limited submissions per day which doesn&#8217;t display the results for a day (or something similar). That way you can still play with your solution on the first set, still be able to make sure the real case will work fine on your code, yet prevent the reverse engineering or mass submissions issues.</p>
<p>e) It was still a great contest <img src='http://blog.codechef.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keshav Dhandhania</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-278</link>
		<dc:creator>Keshav Dhandhania</dc:creator>
		<pubDate>Thu, 16 Jul 2009 05:40:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-278</guid>
		<description>1. &quot;We need to define rules better. ...&quot;
it is not possible for the Admins alone to figure out the crooks. There should be a way for participants to inform the Admin if they suspect anyone. As of now, I don&#039;t know how to inform the Admin regarding such a thing in private. Apologies if the details have been stated and I have overlooked them.

2. Admin responses in forum
You could leave some of the queries to be answered by the community. But there should be upper limit, as in if a query has been unanswered for more than some number of hours, then it must be looked into by the Admin himself without more wait.

3. I love the contests. Keep them going! :)</description>
		<content:encoded><![CDATA[<p>1. &#8220;We need to define rules better. &#8230;&#8221;<br />
it is not possible for the Admins alone to figure out the crooks. There should be a way for participants to inform the Admin if they suspect anyone. As of now, I don&#8217;t know how to inform the Admin regarding such a thing in private. Apologies if the details have been stated and I have overlooked them.</p>
<p>2. Admin responses in forum<br />
You could leave some of the queries to be answered by the community. But there should be upper limit, as in if a query has been unanswered for more than some number of hours, then it must be looked into by the Admin himself without more wait.</p>
<p>3. I love the contests. Keep them going! <img src='http://blog.codechef.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keshav Dhandhania</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-1684</link>
		<dc:creator>Keshav Dhandhania</dc:creator>
		<pubDate>Thu, 16 Jul 2009 05:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-1684</guid>
		<description>1. &quot;We need to define rules better. ...&quot;
it is not possible for the Admins alone to figure out the crooks. There should be a way for participants to inform the Admin if they suspect anyone. As of now, I don&#039;t know how to inform the Admin regarding such a thing in private. Apologies if the details have been stated and I have overlooked them.

2. Admin responses in forum
You could leave some of the queries to be answered by the community. But there should be upper limit, as in if a query has been unanswered for more than some number of hours, then it must be looked into by the Admin himself without more wait.

3. I love the contests. Keep them going! :)</description>
		<content:encoded><![CDATA[<p>1. &#8220;We need to define rules better. &#8230;&#8221;<br />
it is not possible for the Admins alone to figure out the crooks. There should be a way for participants to inform the Admin if they suspect anyone. As of now, I don&#8217;t know how to inform the Admin regarding such a thing in private. Apologies if the details have been stated and I have overlooked them.</p>
<p>2. Admin responses in forum<br />
You could leave some of the queries to be answered by the community. But there should be upper limit, as in if a query has been unanswered for more than some number of hours, then it must be looked into by the Admin himself without more wait.</p>
<p>3. I love the contests. Keep them going! <img src='http://blog.codechef.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hemant Verma</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-277</link>
		<dc:creator>Hemant Verma</dc:creator>
		<pubDate>Wed, 15 Jul 2009 15:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-277</guid>
		<description>I suggest for challenge problem , data will be random like we have any Topcoder Marathon Matches . Also the length of problem statement must be limited so that coding contest not turnout english tests.</description>
		<content:encoded><![CDATA[<p>I suggest for challenge problem , data will be random like we have any Topcoder Marathon Matches . Also the length of problem statement must be limited so that coding contest not turnout english tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hemant Verma</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-1683</link>
		<dc:creator>Hemant Verma</dc:creator>
		<pubDate>Wed, 15 Jul 2009 15:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-1683</guid>
		<description>I suggest for challenge problem , data will be random like we have any Topcoder Marathon Matches . Also the length of problem statement must be limited so that coding contest not turnout english tests.</description>
		<content:encoded><![CDATA[<p>I suggest for challenge problem , data will be random like we have any Topcoder Marathon Matches . Also the length of problem statement must be limited so that coding contest not turnout english tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neelesh</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-276</link>
		<dc:creator>Neelesh</dc:creator>
		<pubDate>Wed, 15 Jul 2009 04:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-276</guid>
		<description>If you are planning to have a very-short duration contest, like 6 hours or 8 hours, then there is no need of a  single tie-breaker. In a short duration contest you can also score a solution based on how fast the coder submits. In fact I think  the main purpose of a short-duration competition is to test the speed of problem solving.</description>
		<content:encoded><![CDATA[<p>If you are planning to have a very-short duration contest, like 6 hours or 8 hours, then there is no need of a  single tie-breaker. In a short duration contest you can also score a solution based on how fast the coder submits. In fact I think  the main purpose of a short-duration competition is to test the speed of problem solving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neelesh</title>
		<link>http://blog.codechef.com/2009/07/13/lessons-learned-from-july-contest/#comment-1682</link>
		<dc:creator>Neelesh</dc:creator>
		<pubDate>Wed, 15 Jul 2009 04:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codechef.com/?p=319#comment-1682</guid>
		<description>If you are planning to have a very-short duration contest, like 6 hours or 8 hours, then there is no need of a  single tie-breaker. In a short duration contest you can also score a solution based on how fast the coder submits. In fact I think  the main purpose of a short-duration competition is to test the speed of problem solving.</description>
		<content:encoded><![CDATA[<p>If you are planning to have a very-short duration contest, like 6 hours or 8 hours, then there is no need of a  single tie-breaker. In a short duration contest you can also score a solution based on how fast the coder submits. In fact I think  the main purpose of a short-duration competition is to test the speed of problem solving.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

