a/usaco-guide
Archived
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Update Contest_Strategy.md

Browse source
This commit is contained in:
nchn27 2020-06-16 19:26:08 -04:00 committed by GitHub
parent e95d7bf955
commit 32e19cf11d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/2_General/Contest_Strategy.md
View file

@ -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.