How to improve constructive algorithms ?
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 3993 |
2 | jiangly | 3743 |
3 | orzdevinwang | 3707 |
4 | Radewoosh | 3627 |
5 | jqdai0815 | 3620 |
6 | Benq | 3564 |
7 | Kevin114514 | 3443 |
8 | ksun48 | 3434 |
9 | Rewinding | 3397 |
10 | Um_nik | 3396 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 155 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
10 | nor | 152 |
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