I know what constructive means, but I cannot tell the difference between constructive and implementation.
| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3408 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 154 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | AmShZ | 146 |
| 5 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | BledDest | 136 |
| 8 | adamant | 135 |
| 9 | maroonrk | 133 |
| 10 | cry | 130 |
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
hahhahaa like it