Rosetta Code:Add a Task: Difference between revisions
→Things to avoid: "Code Golf:" prefix
Thundergnat (talk | contribs) (→Create the page: Formalize a few guidelines for task titles) |
(→Things to avoid: "Code Golf:" prefix) |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 23:
:# The first character after a level separator ( forward solidus: / ) should always be uppercase.
:# Every other word should be lowercase except for proper nouns, names and common initialisms.
There is substantial leeway in these rules, and some are subject to interpretation, but the closer you can come to following them, the easier it will be all-around.
Line 57 ⟶ 58:
***When giving a best effort solution then state near its top, just what aspects of the task are not implemented, to avoid later editors marking the example as incorrect.
***Consider the removal of a prior partial solution to a task when adding a new full solution to the task.
* '''Avoid creating tasks seeking the smallest possible solution.''' Code golf, or the finding of the absolute most succinct expression of a solution as its own goal, is not often an idiomatic, practical or comprehensible use of the language in question, and so is difficult to justify in a demonstrative context. Strokes are not points. For now, the only exception to this rule is [[Code Golf: Code Golf]]. If there is a case to be made for another exception, please use the prefix "Code Golf:" when creating the page.
* '''Avoid creating tasks seeking the fastest possible solution.''' Optimized code is rarely easy to read, and is often exceptionally complex as something to learn from. However, provided it does not make the overall section for the language too long, users may provide a more-optimal solution as an alternative solution to a particular task so that learners can compare it to the “optimized for clarity to people” version that should be the main solution for the language. (We also do not want to see the site devolving into “my language is faster than yours” silliness.)
| |||