Which problem do you think is the best and which is the worst.Share in comments please thanks.
| # | User | Rating |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | jiangly | 3631 |
| 4 | Kevin114514 | 3574 |
| 5 | maroonrk | 3521 |
| 6 | strapple | 3515 |
| 7 | Radewoosh | 3461 |
| 8 | tourist | 3428 |
| 9 | turmax | 3378 |
| 10 | Um_nik | 3376 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 162 |
| 2 | adamant | 148 |
| 3 | Um_nik | 146 |
| 4 | Dominater069 | 143 |
| 5 | errorgorn | 140 |
| 6 | cry | 138 |
| 7 | Proof_by_QED | 136 |
| 8 | YuukiS | 135 |
| 9 | chromate00 | 134 |
| 10 | soullless | 133 |
Which problem do you think is the best and which is the worst.Share in comments please thanks.
| Name |
|---|



All the problems below my rating are the best and the problems above my rating which I can't solve are the worst.
For me, All the problems below my rating are the worst and the problems above my rating which I can currently solve or will be able to solve in the future are the best.
Yep. That's what differentiate a newbie and a International Master. Top notch mentality .
Worst problem: 1207F - Remainder Problem or 1921B - Arranging Cats.
Best problem: 1155E - Guess the Root.
Did you solve that?
All of them. 1921B - Arranging Cats is an extremely complicated one liner. 1207F - Remainder Problem have too low skill levels for a F div2 and requires endl to
\n(terrible). With that in mind it barely passes at a badly 3900+ms.Your problem on 1207F is not on
endl, but this:#define int long longSeriously, if you cast long long on everything and expect nothing bad to come, even with 64-bit processing support, you would have yourself to blame.
The problem being surprisingly easy is an odd trait of educational round as a whole, and I would stay neutral at that — neither enjoying nor hating.
For 1921B, I don't get your point here. The problem is simple as it is. Perhaps skimming and summarizing is something you could do a bit of practice?
i agree, 1921B is not that hard.
AkiLotus, what unexpected problems can occur by using
#define int long long? As a person, who has that in his template, I would like to know that xdIn the simplest sense, double arithmetic runtime and/or memory consumption, due to now the CPU has to do maths in 64-bit instead of 32-bit (worse if the compiler itself only supports 32-bit, as it has to do some unnatural twerk to support something higher than it physically possesses).
there are no bad problems
OK then you liked most
this one
I don't remember all the problems I solved but from the recent problems I solved, a good problem was from ICPC Asia Pacific which is There and back again I had fun solving it and fixing the bugs in my code. and the other was Find a mine it was fun geometry and it's idea was fantastic.
and for the worst, it's not bad but I still remember in Vika and her friends that I have lost brain cells reading the statement and the problem itself was kinda good when someone explained it to me.
My favourite is this
How come 'mine favourite'?
I think it should be 'my favourite'(: