I know what constructive means, but I cannot tell the difference between constructive and implementation.
# | 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 |
# | User | Contrib. |
---|---|---|
1 | Um_nik | 163 |
2 | cry | 161 |
3 | maomao90 | 160 |
4 | -is-this-fft- | 159 |
5 | atcoder_official | 158 |
5 | awoo | 158 |
7 | adamant | 155 |
8 | nor | 154 |
9 | maroonrk | 152 |
10 | Dominater069 | 149 |
I know what constructive means, but I cannot tell the difference between constructive and implementation.
Name |
---|
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