I have solved a lot of problems say 2000 why i have not improved till now?

The number of problems solved means little. I sometimes mention it to show passion for programming (2000+ means a lot of time spent), but it says nothing about the difficulty of the problems you’ve solved.

 You have read a lot of problem statements and are should be comfortable in coding up solutions. Since you haven’t been progressing, you need to work smarter than you have till now.

 I can go to Codeforces or another online judge and solve a few hundred Div2-like problems in little time. Yet, I won’t learn anything.

 By now, you must know the kinds of problems you struggle with. You need to work on those. Since you’re not in Div1, my guess is that you’re not consistently solving Div2D and E problems. Focus on them. Then, move up to Div1 up to problem C.

 When you struggle with a problem, say graph theory, try to study up the theory behind the key ideas and consolidate your knowledge and understanding of it.

 Qualifying for ICPC WF is much trickier. Some regionals are way easier than others. It really depends on where you study. It also depends on whether you can get good team mates or not.

Comments

Post a Comment

Popular posts from this blog

Forget Efficiency and start solving easier problems

Sometimes, you may notice that many programmers solved many problems but they made very few submissions (they are geniuses!). At first, you may think that I should try to solve the problems as less try as possible. So, after solving a problem, you will not want to try it again with other algorithm (may be far far better than the previous algorithm you used to solve that problem) to update your rank in the rank lists. But my opinion is that if you think so you are in a wrong track. You should try other ways as in that and only that way you can know that which of the algorithms is better. Again in that way you will be able to know about various errors than can occur. If you don’t submit, you can’t know it. Perhaps a problem that you solved may be solved with less time in other way. So, my opinion is to try all the ways you know. In a word, if you are a beginner forget about efficiency. Find the easier problems.Those problems are called ADHOC problems. You can find the list of those prob...
Read more

Good schedule to follow for becoming better at competitive programming for beginners

The three most important things in competitive programming: Learn and know your programming language. (~3 months - all the time) Learn algorithms/data structures and implement. (~9 months - all the time) Practice coding every day. Do contests. (all the time) (Doesn’t just apply to competitive programming) Have fun! (all the time) Thus, that’ll be how you break up your schedule. The time it takes for each person will differ, depending on if you already know algorithms, if you know programming or not, etc. The following is a more detailed how: #1 Learn and know your programming language. Pick a programming language and stick with it. Learn the basic syntax and start solving beginner problems. People always ask “how do you learn a programming language?” Search Google and find out; there are so many resources online. (If you really can’t find a resource, message me.) Try out USACO training pages. Or if you don't you can use the CodeChef beginner track: beginner | CodeChe...
Read more

New practice session for all the programmers with me.

So guys sorry i had been missing around for a while due to academic pressure and now i promise that i will keep on updating the blog with exciting and interesting blog posts so all those who are interested to learn competitive programming from scratch can start with me.I will start posting the resources to learn the concept and some problems based on those topics.Good luck. I will  start the training from 5th june.
Read more