so i am practicing 1600 rated problem but i find them difficult to solve stuck on a question from days and even after reading the editorial its still something i can not really understand , can anyone help me or guide me how i should approach problems above 1500 , it would be really helpful if any expert level coder or above can tell me something from there experience?
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | jiangly | 3810 |
| 2 | Benq | 3676 |
| 3 | Kevin114514 | 3655 |
| 4 | maroonrk | 3463 |
| 5 | strapple | 3390 |
| 6 | Um_nik | 3387 |
| 7 | tourist | 3384 |
| 8 | heuristica | 3322 |
| 9 | turmax | 3319 |
| 10 | jiangbowen | 3291 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | Um_nik | 144 |
| 5 | Errichto | 139 |
| 5 | AmShZ | 139 |
| 7 | adamant | 137 |
| 8 | maroonrk | 134 |
| 9 | BledDest | 132 |
| 10 | qwexd | 129 |
I feel like problems around 1600 don't require a lot of depth but more "width". like it won't be a necessarily hard idea, but it may be an idea you never saw. so it might take you a while to solve if you have never seen something similar before but when you finally spot the idea it will be relatively simple to prove/implement/solve. when I was under 1600 I would basically just spam 1600 problems and I would read editorials after 5-10 minutes because it's just more efficient than staring at a screen for an hour.