# | 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 | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | adamant | 157 |
6 | awoo | 157 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | djm03178 | 153 |
Name |
---|
Did you ever use the same strategy of blind challenges in the past? I'm very curious about why you make the decision.
He focused on solutions of low rating coders, which had more probability to be incorrect. Speed was very important in this case, as he wanted to prevent them from being challenged by others. After had made a wrong challenge, he challenged more carefully :D
Yes, I've done this before. In this case I needed something like +200 points, and the problem was tricky, so this seemed like a good gamble.