# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
4 | atcoder_official | 161 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
Name |
---|
I remember that few years ago I was given this exact stock problem on some interview at some company. What followed then was an hour of me stating bunch of false lemmas and being literally clueless about it. I was kinda destroyed that I was rejected not because of I am bad at writing clean code, not because I am bad at some system design or class diagrams, but because I failed at solving algorithmic question which is my beloved hobby, what was a real stain on my honor and dignity. I feel kinda relieved to read that one of the greatest competitive programmers in world wrote "Problem D had deceptively simple statement which led to a lot of frustration as I was unable to come up with its solution for two hours" :P (however I wouldn't call getting it accepted at 2:00 mark as a fifth problem as being unable to solve it for two hours, but you get the point).