When you realize that you need to change your approach while facing a challenging problem? In contests, I always tend to rush and keep optimizing the same solution without knowing when to stop.
→ Pay attention
→ Streams
→ Top rated
| # | User | Rating |
|---|---|---|
| 1 | tourist | 4009 |
| 2 | jiangly | 3773 |
| 3 | Radewoosh | 3646 |
| 4 | ecnerwala | 3624 |
| 5 | jqdai0815 | 3620 |
| 5 | Benq | 3620 |
| 7 | orzdevinwang | 3612 |
| 8 | Geothermal | 3569 |
| 8 | cnnfls_csy | 3569 |
| 10 | Um_nik | 3396 |
→ Top contributors
| # | User | Contrib. |
|---|---|---|
| 1 | Um_nik | 163 |
| 2 | cry | 161 |
| 3 | maomao90 | 160 |
| 4 | -is-this-fft- | 159 |
| 5 | awoo | 158 |
| 5 | atcoder_official | 158 |
| 7 | adamant | 155 |
| 8 | nor | 154 |
| 9 | maroonrk | 152 |
| 10 | Dominater069 | 149 |
→ Find user
→ Recent actions
Codeforces (c) Copyright 2010-2024 Mike Mirzayanov
The only programming contests Web 2.0 platform
Server time: Sep/22/2024 02:14:41 (j3).
Desktop version, switch to mobile version.
Supported by
A strategy I use is check how many people have done the problem. If a lot of people have solved and I am stuck chances are I am doing the wrong approach, probably over complicating things. A lot of people is relative. 8k people done div 2 A? Not a lot. 1k done div 2 D? This is a lot and chances are this one is easier than most div 2 D.