Timeline for answer to Things to avoid when writing challenges by Sp3000
Current License: CC BY-SA 3.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2018 at 10:55 | comment | added | l4m2 | I think it's a "don't just combine two challenges"? (assuming some basic challenges were there for long time) | |
| Mar 16, 2017 at 16:38 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:38 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:38 | history | edited | CommunityBot |
replaced http://meta.codegolf.stackexchange.com/ with https://codegolf.meta.stackexchange.com/
|
|
| Jun 17, 2016 at 14:41 | comment | added | Sp3000 | @Zgarb The emphasis was meant to be on "when there's no good alternative approaches" :) (I should probably add that the only reason they're there is because there's been such examples in the past) | |
| Jun 17, 2016 at 14:16 | comment | added | Zgarb |
The last two bullet points are debatable, especially when f is simple, since there may be (more or less obvious) shortcuts. Case in point.
|
|
| Jun 16, 2016 at 11:21 | history | answered | Sp3000 | CC BY-SA 3.0 |