How to improve constructive algorithms ?
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 166 |
2 | maomao90 | 163 |
2 | Um_nik | 163 |
4 | atcoder_official | 161 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | nor | 153 |
9 | Dominater069 | 153 |
How to improve constructive algorithms ?
Название |
---|
DO's: Making a blog about it
DONT's: Practice
you should solve 'constructive' tagged problems a lot in a problemset. no other ways.
I think you should solve constructive problems, but the "constructive" tag in Codeforces problemset can mean pretty much any problem, so I wouldn't suggest that.
So probably just solve problems rated around 1000 — 1400 from the problemset, I find that it helps me solve the earlier problems (A and most of the time B) faster, so I have more time to solve the later problems (C, sometimes D, and hopefully E soon!).
you can refer to this lecture