Rosetta Code:Add a Task: Difference between revisions
→Task focus exclusion: Bullet again.
(→Task focus exclusion: Reword to reduce highlighted section.) |
(→Task focus exclusion: Bullet again.) |
||
Line 27:
===Task focus exclusion===
* '''Don't require a specific language.''' Tasks which specify a particular language will not tend to achieve many useful comparisons or solutions, as languages are the richest resource on Rosetta Code. If your personal goal is to create a task which highlights a feature of a particular language, where that feature is unique or extraordinarily rare, don't create a task where that feature is ''required'' to solve the task. Instead, create a task that can be solved using a variety of means, but where that feature can greatly help in solving it. You may wish to highlight a unique feature of a particular language (yes, there are specific language advocates on Rosetta Code, and that's fine), but nobody will see that feature's usefulness if there are very few other languages for them to compare against.
* '''Don't
* '''Best-effort solutions are often fine''' A caveat to the above notes is that some example solutions can fudge the spec without being inappropriate. ''"This isn't exactly possible in Ayrch, but something practical solving the language's idiomatic analog would be..."''
▲'''Don't be too specific.''' Requring unique language features, or rare combinations of features, leads to the same problems as requiring a specific language.
===Basic information===
| |||