Long time ago during the challenge phase I found method called 'saiki' in the code of one participant from Japan.

Just out of interest, I tried to translate it, turns out that:

saiki = さいき (hiragana) = recursion

saiki = サイキ (katakana) = psyche

(by the way,  it would be cool to know which books are good to learn Japanese).

I wonder what's happening with me last time.

Let me tell you my short story.

During the "Unknown language contest #1" I've spent too much time on solving relatively easy task (D). So, when I solved E it was about 40 seconds before the end of the contest. When I saw it, my eyes popped out and I was trying to find this file to submit. The only problem is that when you have no time, your hands don't obey. But I did it, in about last 30 seconds, yoohoo! And even system tests were passed.

During the "Codeforces Beta Round #58" my solution on task B was hacked. I was trying to find my mistakes, but.. there is no mistakes in my code! Then I understand, that "int" is too small to store values that I need. I've changed it to "long" and judje's verdict was "MLE". Ok, I killed one array. And now judje's verdict was "TLE" on the hacker's test.

And, SUDDENLY, I realized, that Java's Scanner is tooo slooooow (maybe, it's God's punishment for moving from C++) . I wrote new solution using StreamTokenizer (thanks to http://acm.timus.ru/help.aspx?topic=java). And I've submitted this task in last 6 seconds (!!!). 

It's too sad that due to lack of the time I didn't hack any Java solution.

I can't describe my feelings when submitting those tasks, I just remember that it is like... electric shock or something that I can't write here :)

p.s. Sorry for my bad english, feel free to point on my mistakes.

Захотелось мне посмотреть самые быстрые решения.

Но в результате увидел только решения с ошибкой компиляции и временем работы 0 мс.

Может, стоит сделать галочку "Только Accepted" или что-то вроде того?