Hi there, I tried cp couple of times. Every time I failed and gave up. I don't know where is the issue. I open a random problem and try to solve it. I usually give a shot for 20-30 mins. Some times I came up with a brute force approach and submit the problem. Usually it fails. Then i took the help of chatgpt.
USACO guide is a good resource ig. Should I solve problem topic wise? or randomly solve it? How I can i improve my cp skills?
Thanks in advance.
fahadhossainbabor2103114 Give all contest, and do virtual contests if there is no contest on that day. If you even solve 1 problem try upsolving the others, look at great coders code and read editorial even if you solve a problem to see if there is more to learn ;)
Just solve problems rating wise from problemset. First start with 900 rating problems. solve min 50+ problems. then if you are comfortable than move to 1000 rating problems. in this way continue practicing. and in the mean time learn some basic topics like prefix sum, binary search, stl, sliding window etc.... you will find many resources and roadmaps in both bengali and english in this link... hope this will help you... https://codeforces.com/blog/entry/122788
Thanks man. Means a lot
if you are new to a certain topic, you can solve topic wise till you get compfortable with that topic, but after wards it is not recomended because if you already know the tags of a problem, you have some clue about that.
20-30 mins is a pretty short time. I would say try for at least ~45 minutes.
If you flat out can't solve any problems, I'd say shift ot slightly easier ones.
Please can you tell? Should I give ~45 min time for 800-1000 rated problems too? OR for higher rated problems?
It's like training your muscles, use progressive overload.
Work on problems that you are barely to solve in 45 minutes. If 1000-rated problems take you around 45 minutes, then that's what you should do.
Expect to take longer than that sometimes. If you never miss the deadline, the problems you're doing are probably too easy for you.
In the cases when you fail, you may read the editorial or try the problem again after a few days.
To be honest I recommend longer than 45 minutes (I prefer something like 2 hours) but feel free to adjust this to suit your learning style.
Personally what I did was try until I spent one hour with absolutely no progress. Then I would peek at the editorial, then try for another hour. This doesn't mean one hour total, this means if I spent 20 minutes thinking, then 20 minutes coding, then 1 hour debugging without figuring out the issue, I would look at the editorial. Then I'd repeat, and if I get stuck again I would look at the code. For Olympiad problems that tend to be harder, I try to avoid looking at the editorial at all (which sometimes led to my spending 6+ hours on a single problem...)
try it for 1 hour, if you can't solve it, read the editorial and try again, if you still don't understand, owari da, try another problem
stop using tutorial's. You see? You sometimes need to do for a few years a problem in order to solve it, that is without tutorial.