Ahem..

First of all we are sorry that it's too late.

Let me tell you a common problem I face in contests.

"I read the problem statement and I understand that pretty well. But either I don't know how to approach or I get stuck in fixing bugs."

Sometimes it takes more than an hour to fix the bugs and the contest ends.

This is a common scenario for beginners like me.

For a beginner normally there are 3 types of problems in a contest ( especially in onsite ones). (Maybe these are true for experts too :p)

1. They understands the problem but can get AC because of lack of bug-free coding skills.
2. They understands nothing of a problem.
3. They understands well and get AC for 1-3 problems.

There are hundreds of ways and nothing is bad at all.

You need to choose the one you feel comfortable.

Let me tell you something. If you don't like this, go on, find your own and let others know who need your help.

Stage 1:

• Start with C. (Know about some header files and their features)
• Open account in UVa Online Judge
• Insert your UVa user name @uHunt Tool
• Solve at least 200 problems (Any 200, Ad-hoc, String etc.)
• Solve problems from Math section as many as possible.
• Learn C++ (It should not take more than 2 days)
• Learn C++ STLs and built-in algorithms. And some necessary stuff like Two pointer, Bit manipulation etc.
• Solve some problems from uHunt's Data Str...

There are dozens of online judges and it's not a mission to solve all the problems :p.

But we will pick the problems which are necessary for our training.

Besides, we will try to participate in as many contests as possible.

Till now we have this list (In no particular order):

Have eyes on these for regular contests:

• CodeForces
• HackerRank
• CodeChef
• TopCoder
• USACO