From 32e19cf11d79bcc58d3f1c0b11612e6cdc4503e7 Mon Sep 17 00:00:00 2001 From: nchn27 <46332369+nchn27@users.noreply.github.com> Date: Tue, 16 Jun 2020 19:26:08 -0400 Subject: [PATCH] Update Contest_Strategy.md --- content/2_General/Contest_Strategy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/2_General/Contest_Strategy.md b/content/2_General/Contest_Strategy.md index 48d6916..19c99f0 100644 --- a/content/2_General/Contest_Strategy.md +++ b/content/2_General/Contest_Strategy.md @@ -15,7 +15,7 @@ Strategy is flexible and all advice should be taken with a grain of salt. Strate You should read *all* the problems first (don't give up on any problems prematurely). Generally, a lot of thinking should happen before any coding. Depending on the difficulty of a contest, you can spend anywhere from 5 minutes to 2 hours with a pencil and paper before touching the keyboard. Sometimes, problem difficulties can be out of order, so keep that in mind before focusing down three hours on problem 1 and not getting anywhere. ### Time allocation -It's the worst feeling in the world to sink 4 hours into a problem, then not get it, only for another problem to have an easier solution. It's hard to know what is an easy and what is hard when you don't know the solution yet, so you have to use your own judgement in deciding what is likely solvable and what should be quit. Generally, don't spend "too long" on one problem, and stay away from problems that look like they test something you don't know well. +It's the worst feeling in the world to sink 4 hours into a problem, then not get it, only for another problem to have an easier solution. It's hard to know what is easy and what is hard when you don't even know the solutions, so you have to use your own judgement in deciding what is likely solvable and what should be quit. Generally, don't spend "too long" on one problem, and stay away from problems that look like they test something you don't know well. ### When you see a solution If you immediately get the solution to a problem while reading it, it might be a good idea to code it up quickly and get it out of the way.