10

Use the sandbox to "defend" your challenge The sandbox is meant to be an aid to improve the challenge. But once posted to the main site, the quality of the challenge is entirely the poster's responsibility. Regardless of the sandbox, the challenge on the main site should be solid and well specified. If you post to the main site and the challenge is ...


8

As far as I can see, there are two big issues here that both need addressing: Visibility of useful resources How helpful those resources are Visibility No one likes having a whole bunch of links to a whole bunch of posts thrust into their face as soon as they do anything. That said, some links are close to essential for new users in order to properly ...


5

Warnings From what I can tell, the review screen is somewhat customizable. It doesn't seem like it can test for not having a tag (i.e., not having an objective winning criterion), but we can add regex based warnings for the body or tags. I suggest the following: Language tags Some of the more common of these, like javascript, java, c, etc., with warnings ...


5

Think twice if you're writing a challenge around an algorithm you found on the Internet Simply put, it will never work as you expect, (though it could work as "a challenge") unless you pick your algorithm and the problem very carefully. If you make it a plain code-golf without any restrictions, answers are free to choose brute force (which works ...


5

Multipart challenges with unrelated sub-tasks In general, a challenge on Code Golf should focus on a single core task. Challenges with multiple sub-tasks are discouraged, especially when the sub-tasks have zero or very little interaction or common aspects. If the answer to at least one of the following questions is "yes", your challenge has a high ...


Only top voted, non community-wiki answers of a minimum length are eligible