I know what constructive means, but I cannot tell the difference between constructive and implementation.
№ | Пользователь | Рейтинг |
---|---|---|
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 | 156 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
9 | nor | 153 |
I know what constructive means, but I cannot tell the difference between constructive and implementation.
Название |
---|
They are orthogonal.
Constructive: you need to generate an object satisfying some particular properties, this requires non-trivial thinking.
Implementation: the solution is relatively easy to come up with, but difficult to implement (e.g. the code is long, bugs can be introduced easily, there are many possible off-by-one errors, etc.).
You can think of the 'constructive' tag as a measure of how much ad-hoc thinking is necessary, and of 'implementation' tag as a measure of how much programming and debugging skills are required.
first one takes either 0 or 10 milion years to think and 0 seconda to code and the other one takes 0 seconds to think and 10 milion years to code