What should I do if I don’t understand a problem statement(like this problem)?
# | 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 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
What should I do if I don’t understand a problem statement(like this problem)?
Name |
---|
You need to the read the explanation for sample test cases carefully. And come back to reading the question again. Most of the times when I didn't get a question, I understand that question by the explanation for sample test cases.
Thanks. Actually I can usually get the problem statement of problem A and B in educational rounds, Div.2 rounds, and Div.3 rounds so it doesn't matter a lot. This is the only problem I can't understang when I'm doing contests.
https://codeforces.me/blog/entry/76348?#comment-609448
Thanks!
You must downvote the shit out of the announcement.
My experience is when the state is too long and hard to read. Then you try to find the keywords (some what I think must have paid attention to be able to solve). Then I try to observe from the Example, how can input -> output, read the explanation if posisble.
Then I re-read the statement again. But in this time if I still dont understand I change the problem.
Thanks!