The slide deck is locked
Sign in below to open the deck and the rest of the write-up.
What we covered
Most people lose contests before they write a line of code, by misreading the problem or reaching for an algorithm they half-remember. The session spends its time on the thinking that happens before the editor is open, then names the algorithms worth actually knowing.
- What competitive programming is: solving problems by coding correct solutions inside a fixed window of time.
- Why do it at all: testing yourself, learning fast, recognition, networking, and the jobs it opens.
- The shape of a contest: understanding the problem, reading the input and output, choosing an approach, coding, testing, submitting.
- Problem solving as the foundation, with the buffet-table analogy: survey everything on offer before committing to a plate.
- A method for coding a solution: read it more than once, solve it by hand against the samples, tighten the steps, write the pseudocode, then implement and refine.
- The reduction trick: shrink the problem to a smaller version, solve that, and scale the solution back up.
- Preparing between contests: consistent practice, algorithm coverage, familiarity with the contest environment, solving on paper, and sleep.
- The algorithm categories that keep coming back, from the basics through to advanced data structures.
- Where to keep going, starting with USACO Training.
Members only
Keep reading
The slide deck and the rest of this write-up are free, sign in with Google and they stay unlocked on this device.
No newsletter, no spam. Your email is used to keep you signed in.