@admin
Making global limit for all submissions (even 10-15 seconds) is very bad for short contests.
IMHO the only thing to do is to restrict gap between submissions of challenge problems to say 30 or even 60 seconds. Then such situation will not happen again.
Actually this time due to nature of challenge problem I made 10 tabs with submit page and when I do some change in the solution I submit it 10 times (from each opened tab) to see what it is actual average score
@n2n_ >> He meant he submitted 10 times with minor tweaks in all. All being different from each other by some tiny things. NOT submitting the exact same code 10 times.
@bugkiller << In my case the score for the same code could vary in the range of size about 70 points. Check for example my 10 consecutive submissions from 2152975 to 2152997 here. The minimal score is 9209 while the maximum is 9275. So submitting the same code several times was very useful for this problem.
@anton_lunyov >> thats interesting then. I would really like to know how you approached by subsequent submissions, would also like everyone who got a score > 0.95 to share their ideas behind their subsequent algorithms; as I felt this problem was one of the best challenge problems yet.
@betlista, In short contests, if you get a compilation error, you get a penalty of 20 minutes. I think you can take a few extra seconds to remove the public modifier and then submit. Wonβt take even 30 seconds, and saves you the penalty!!