Which problem do you think is the best and which is the worst.Share in comments please thanks.
Which problem do you think is the best and which is the worst.Share in comments please thanks.
# | User | Rating |
---|---|---|
1 | tourist | 3690 |
2 | jiangly | 3647 |
3 | Benq | 3581 |
4 | orzdevinwang | 3570 |
5 | Geothermal | 3569 |
5 | cnnfls_csy | 3569 |
7 | Radewoosh | 3509 |
8 | ecnerwala | 3486 |
9 | jqdai0815 | 3474 |
10 | gyh20 | 3447 |
# | User | Contrib. |
---|---|---|
1 | maomao90 | 174 |
2 | awoo | 164 |
3 | adamant | 163 |
4 | TheScrasse | 160 |
5 | nor | 158 |
6 | maroonrk | 156 |
7 | -is-this-fft- | 152 |
8 | orz | 146 |
9 | pajenegod | 145 |
9 | SecondThread | 145 |
Name |
---|
All the problems below my rating are the best and the problems above my rating which I can't solve are the worst.
OK I understand but I mean problems that you solved or watched editorial....
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 .
why?
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 long
Seriously, 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).
i also imagine some functions might have an unexcepted behavior like with
__built_clz
since it takes in an int, but there is no errors, if you pass in a long long value. thanksWorst: Zero Quantity Maximization because it doesn't get AC without io sync. Best: White Black Balanced subtrees (loved solving it) and Rudolph and Ball Game
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'(:
Can't think of best, but worst problem: https://codeforces.com/contest/1945/problem/C
Agree with this