You are not logged in. Please login at to post your questions!


Tips for short contests

What are some tips to do well in short contests?

asked 20 Jun '17, 00:29

simha's gravatar image

accept rate: 0%

edited 20 Jun '17, 00:30

Answer is hidden as author is suspended. Click here to view.

answered 04 Jul '17, 22:23

raj79's gravatar image

accept rate: 10%

My worst enemy in short contests is the time crunch. You have got to be fast in understanding the Q, developing your algorithm, solving it, and lastly DEBUGGING your code. The last step takes more than half of my time.

Also, make sure you're in contest till very last. I kinda gave up somewhere around ~11:20, and today i saw that contest was extended by 30 minutes. Yes, those 40 minutes felt short to be, but another half an hour would have meant another AC.

Make sure you keep checking the problem list. It might be that you're solving the toughest first, when its recommended to solve easier ones first. I started out with KNICOV, and then went to CHEFADET (ya, serious luck...). After 40 minutes i refreshed the list and gave first 2 Q (Snackup and that "Ada and Crayon" one) a try, and got AC.

Even I am eager to hear some tips from others for short contest. Time crunch is the worst thing in short Q. The questions aren't impossible, but...they take time in my case.

(I will appreciate if anyone can give me tips for my time crunch. My major time goes in debugging my code for WA, corner cases and stuff :( )


answered 20 Jun '17, 00:37

vijju123's gravatar image

5★vijju123 ♦♦
accept rate: 18%

I completely agree with @vijju123 at this point.
Time is your main enemy in this type of challenges. In Long Contest you get enough time to think an appropriate algorithm or maybe even learn new algorithm in the mean-time as well.
Also remember that : Every problem has same points regardless of its difficulty level in Cook-Offs. Hence, your aim will be to solve as many problems as possible but in sorted manner of difficulty!
Hope it helped :)


answered 20 Jun '17, 00:45

dishant_18's gravatar image

accept rate: 12%


Yup. I remember taking 1-2 days to solve problem in Long. Thats why i feel long contests are best to learn, and short best to perform.

(20 Jun '17, 00:49) vijju123 ♦♦5★

I think You should always read all the questions first, and then sort them according to your understanding of the questions. Once this is done, always go for the third easiest. Yes, Keep on doing that until half time. Then Switch to the easiest 2 questions..irrespective of whether the third ques was done or not.! After doing the easiest 2 questions, again go on the third question. IF it is done, then go for 4th and then 5th.! I have applied this strategy in the past 3 short contests, and I think it is a good strategy.!


answered 04 Jul '17, 21:26

iamabjain's gravatar image

accept rate: 6%

I always prefer going for the easiest one. But, how do you know which is the easiest? The simplest way is to wait for 1-2 minutes and see which problem has been solved. That's the easiest one. You may read any problem in that time but waiting not more than 2 minutes is still far far better than concentrating on a problem which maybe is tougher than most of the problems and waste a lot of time in that problem.

So now, what if one doesn't want to waste those 1-2 minutes, because every second is crucial in a short contest. I can tell what I do in that time. I look at the input, output and constraints of each problem. Usually, simple adhoc problems have simple input, output and also the constraints will be reasonable. I try to look at these to find easier problems and usually it works(not always).

Hope it helps! :)


answered 04 Jul '17, 22:56

sudip_95's gravatar image

accept rate: 10%

Answer is hidden as author is suspended. Click here to view.

answered 04 Jul '17, 22:21

raj79's gravatar image

accept rate: 10%

toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported
  • mathemetical formulas in Latex between $ symbol

Question tags:


question asked: 20 Jun '17, 00:29

question was seen: 787 times

last updated: 04 Jul '17, 22:56