http://petr-mitrichev.blogspot.com/2014/03/this-week-in-competitive-programming.html

http://petr-mitrichev.blogspot.ru/2014/02/this-week-in-competitive-programming.html

http://petr-mitrichev.blogspot.ru/2014/01/this-week-in-competitive-programming_27.html

http://petr-mitrichev.blogspot.ch/2014/01/this-week-in-competitive-programming_20.html

http://petr-mitrichev.blogspot.ru/2014/01/this-week-in-competitive-programming_12.html

http://petr-mitrichev.blogspot.ru/2014/01/this-week-in-competitive-programming.html

http://petr-mitrichev.blogspot.ru/2013/12/this-week-in-competitive-programming_30.html

http://petr-mitrichev.blogspot.ru/2013/12/this-week-in-competitive-programming_22.html

http://petr-mitrichev.blogspot.ru/2013/12/this-week-in-competitive-programming_16.html

http://petr-mitrichev.blogspot.ru/2013/12/the-decisive-topcoder-open-finals-hard.html

http://petr-mitrichev.blogspot.ru/2013/12/this-week-in-competitive-programming_9.html

http://petr-mitrichev.blogspot.ru/2013/12/this-week-in-competitive-programming.html

http://petr-mitrichev.blogspot.ru/2013/11/this-week-in-competitive-programming_24.html

http://petr-mitrichev.blogspot.ru/2013/11/this-week-in-competitive-programming_18.html

http://petr-mitrichev.blogspot.ru/2013/11/topcoder-open-2013-algorithm-finals-day.html

http://petr-mitrichev.blogspot.ru/2013/11/this-week-in-competitive-programming_18.html

http://petr-mitrichev.blogspot.com/2013/11/this-week-in-competitive-programming_11.html

http://petr-mitrichev.blogspot.com/2013/11/topcoder-open-2013-marathon-competition.html

http://petr-mitrichev.blogspot.ru/2013/11/this-week-in-competitive-programming.html

http://petr-mitrichev.blogspot.ru/2013/10/this-week-in-competitive-programming_27.html

http://petr-mitrichev.blogspot.com/2013/09/codeforces-round-201-and-heart-rate.html

http://petr-mitrichev.blogspot.ru/2013/07/acm-icpc-2013-world-finals-practice.html

http://petr-mitrichev.blogspot.ru/2013/05/ural-championship-aftermath.html

http://petr-mitrichev.blogspot.ru/2013/05/ural-championship-day-1-russia-vs-china.html

Через час (20:30 по Московскому времени) должен начаться финал Facebook Hacker Cup. Есть шанс, что начало будет перенесено на час, так как вчера нам выдали ноуты для подготовки только в 10 вечера. Финал длится 3 часа. Результатов и задач в инете, как я понимаю, нигде не будет :)

Уже завтра состоится финал Facebook Hacker Cup 2013. Сам контест с 20:30 до 23:30 субботы по московскому времени, если не будет проблем.

Сижу на первом этаже гостиницы, завтракаю. Все, вы где? У вас же тоже джетлаг, спускайтесь что ли тоже на завтрак, фейсбук платит :)

In the discussion at http://codeforces.net/blog/entry/6870#comment-125383 it became apparent that Jacob has submitted a solution for Round 172 Problem E that passed all system tests, and was not challenged, but in the end he didn't get the score for it because a tester has decided to stress-test it against a correct solution and add tests where it fails to the system test.

I think this is an awful, awful decision, as it goes against the spirit of progamming competitions: automatic judging and complete objectivity it gives.

There are so many ways this can discriminate against Jacob:

• Had I submitted a solution for problem E, the tester might not suspect it would be a wrong greedy (because I'm in top 10 by rating) and would not add tests, and I'd get the points.

• Maybe some people who opted for solving problem D instead also submitted wrong solutions, but since there were more than one of them, the testers did not think to stress-test them.

• Had he submitted his solution right before the end of the contest, the tester might not decide to read it because he'd have other things to do.

But these points are minor compared to the main point, which I want to reiterate:

• This breaks everyone's faith that the competition is fair and objective. The beauty and appeal of programming competitions, in my opinion, relies on this one aspect: automatic judging. Please don't take it away from us.

In this particular situation, I propose to remove the tests in question and give Jacob the score for this problem. In the future, I propose to keep to the formal procedure — use the tests prepared before the contest plus successful hacks. This is the only way to make sure the competition is not subjective.

I don't blame the particular author or tester for this problem — I actually applaud them for bringing this problem to light and explaining their actions clearly. Thanks a lot! Hopefully we can learn from this situation and avoid similar issues in the future.

Завтра буду писать блог про полуфинал на http://petr-mitrichev.blogspot.com/