# | 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 | 166 |
2 | maomao90 | 163 |
2 | Um_nik | 163 |
4 | atcoder_official | 161 |
5 | adamant | 160 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | nor | 153 |
9 | Dominater069 | 153 |
Name |
---|
why
At first, I wanted to fill whole profile activity bar with dark green for the meme. It didn't really matter for me what problems I solve to achieve that, so I've been solving 800* problems obviously. Few months in it became a routine and fun way to pass the time.
when
About 20 minutes ago
Any problems where you struggled ?
Honestly, yes, there'd been about 2-3 constructive problems at which I had to think about 20 or more minutes. I think there even was one that I had to read editorial for. Sadly I remember none of them.
why waste time on easy problems?
First of all, I've noticed that my performance at solving Div2 A-C have increased drastically over past year. Another thing is that my ultimate goal is to clear up whole codeforces's problemset which is quite unrealistic, but it's worth a try. Other reasons had been explained above.
I think I'll try a strategy similar to yours to help increase my speed on div2 A-C. I don't think I'll try to finish everything though. Hopefully it works.
how much time you spend on a problem before looking at the editorial?
Depends on the problem, but most of the time I try to solve the problem without editorial until I'm annoyed with the problem or/and I'm not progressing at finding any observations for a long time. Also if I find my approach unnecessary complicated after solving the problem, I read the editorial to check whether there exists some simpler approach.
What about 800-1300 problems not solvable with C++?
I will solve them someday when I feel like learning languages like J or Q#.
Edit: I guess Q# is an only issue rn.
Q# is cool, you'll love it :)
I may not be the best person to ask for these things, but since this is AMA... In terms of profile review, I think you're doing good job upsolving contests you're taking part in (at least for recent contests). IMO you should focus on learning DSA on level not higher than segment tree (eg. binary lifting, difference array) and also look out for observations commonly reappearing in problems. (eg. $$$GCD(x, x+1) = 1$$$ or harmonic sequence sum upperbound)
Depends on contest's rules, but IMO most often solving 4 tasks slowly will be better in terms of ranking rather than fast solving 3
what happened on fifteenth of february?
I don't really know what you're asking about, I'm assuming you're asking me about the blank spot you're seeing at activity bar. It is caused by differing timezones, so according to your timezone, I haven't solved any problem that day.
Why are some problems not solvable with C++?
Because some problems are part of special contests that allow only specific language. Example problem
Do you feel it helped you solidify previous concepts and it'll help you solve harder problems like 1400+?
Not really, because there aren't too many concepts that you can base easy problems on. I wouldn't recommend solving these problems for practice to anyone, unless you're a newbie or you really want to practice fast-solving easy problems.
Do you recommend us greys to solve as many 1100, 1200, 1300 to go green?
I wouldn't go for quantity but rather quality. Whenever you solve a problem, try to fully concepts that appeared in it. Also from my experience, to get to pupil you don't even have to know any DSA except STL and maybe binary search, so try focusing on that. Very basic graph theory might come in handy too sometimes. Example problem
I've solved all 800-1300 rated problems solvable with C++
Gitgud
nice job
Thanks for setting up this mashup.
Hey I struggle sometimes in 1300 can you please tell what the most focused and basic thing you notice that every 1300 problem must not solved like any theorem or what : (
I think most of the things are explained here.
I will ask again: why?
I don't know if I can come up with any more reasons, I just think it is fun way (for me) to pass time. I think the best comparison to this may be solving sudokus. Most commonly people will solve sudokus not for the real challenge, but rather to pass the time, because it's fun to solve them.
do you have more fun when solving 10 1200's in a hour or spending 2-3 hours on a 2400 problem
Depends on the problem quality, while grinding 800-1300* I sometimes (but rather rarely) had "Wow, idea used in this problem is really cool and original" moments. Example problem It also depends on my mood, but if I had to choose, then I'd select 2400 problem.
Struggle a lot with DP problems any help you got?
Depends on your problem, do you struggle with modelling dp solutions, implementation, or finding optimizations to your dp's?
implementation and modelling.
In terms of implementation, I'd focus on learning top-down approach, IMO recursive dp's are much more intuitive than iterative ones. (as long as you know how to use recursion) I don't know how to help you with modelling part though. Best I can do is recommend solving whole CSES dp section as it contains some very classical dp tasks which you may benefit from.
How can I see the graph/bar chart of solved problems according to their rating ?
Chrome extension called CF Analytics
Thanksssss a lot!
How long do you expect to solve every problem < 2100?
If I manage to ever do that, I think it'll take atleast 2 years from now.
Can you please review my profile?
:)Glad to see your suggestions so that I can improve.
I'll just give some general ideas on how to improve, because it is hard to find your weak spots just by looking at your profile.
Thanks a lot for your suggestion.
I have one doubt, after the contest I upsolve most of the time but after 2 or 3 weeks of that contest if I again try those upsolved problems then I got stuck in it.
Is this thing normal or not?
Well, it is normal to forget things. Whenever you encounter hard problem I'd recommend trying to explain solution in simple terms to someone (or yourself if you have no one to talk to). "If you can’t explain it to a six-year-old, then you don’t understand it yourself", but of course take this quote with a grain of salt.
Please review my profile too
Congrats :)
Thanks, but honestly I wouldn't call that an achievement.
but still, you spent a lot of time on this, good luck with solving rest of the problems
.
It's pretty hard (if not impossible) to point out some particular things that helped me achieved it. I'd say majority of CP-algo is what contributed the most to me.
Did you takes notes when you learn some new topics
I'm never making notes on anything (unless i'm making calculations), so no. Whenever I learn new CP concept/algorithm I write it's implementation or solve problem related to it.
Any advice on constructive problems?
Congratulations! I enjoy doing the same. I have solved all (but few) 800-1600 problems solvable in Java. I am going through 1700s now. I am keeping few easy ones unsolved for a vacation where I don't want to spend too much time on Codeforces, but still like to solve 3+ problems a day ;-).
My kudos. I wish I had such consistency.
Are you happy in life?
Ye, pretty much.
you forget to solve this problem bro.
It is not solvable with C++.
Hi,Bro. I am also trying to make at least a year or 500 days stack in activity bar. But I did't make it all dark green. I am a beginner so I mostly solved 800-1000 rated problem. Nowadays, I am trying to solve 1100-1400 rated problem. I solved most of the problems in C but for now I am using C and C++ both. Wish me Luck : )