Chapter 137
HomeThe first skill of competitive programming is reading problems efficiently. Contest statements are dense — learn to extract the core problem in 30 seconds.
1. Read the sample (30s)
Skip the story. Look at the sample input/output — that's the problem in miniature.
2. Identify the format (15s)
Input constraints, output format, time/memory limits. N ≤ what? T = number of test cases?
3. Read the statement (60s)
Now read the problem. Ignore flavour text. Focus on: input, operation, output.
4. Verify with sample (15s)
Check your understanding by manually tracing the sample.
💡 The 2-minute rule
If you don't have a plan after 2 minutes, re-read. If still stuck after 5 minutes, skip and come back. Don't burn 30 minutes on one problem. In a 2-hour contest, 5 problems = ~20 minutes per problem.