Rosetta Code:Add a Task: Difference between revisions
Content added Content deleted
(→Basic information: sample input is only sometimes needed) |
|||
| Line 3: | Line 3: | ||
===Draft vs non-draft=== |
===Draft vs non-draft=== |
||
<!-- discuss using [[Template:draft task]] before [[Template:task]], to let the community offer feedback on ambiguity and other matters --> |
<!-- discuss using [[Template:draft task]] before [[Template:task]], to let the community offer feedback on ambiguity and other matters --> |
||
* If there is some question on the general suitability of the task then create a draft task and discuss the reason for it being a draft in the talk page. <br> This will warn potential contributors that there may be substantial changes in the task description whilst still in draft status.<br> Reasons for draft status might include, but not be limited to: |
|||
** A task that is too large. |
|||
** A task that is too general and so hard to compare implementations. |
|||
** A task that may be too specific and so only implementable by a single language. |
|||
** ... |
|||
===Task focus inclusion=== |
===Task focus inclusion=== |
||
Generally speaking, the goal is to address a problem a programmer may face or want to think about. This could be a practical problem, a demonstrative one, or even one of entertainment. However, the common theme across all tasks needs to be increasing competence and understanding of the tools in question, by example or by annotated counterexample if necessary. |
Generally speaking, the goal is to address a problem a programmer may face or want to think about. This could be a practical problem, a demonstrative one, or even one of entertainment. However, the common theme across all tasks needs to be increasing competence and understanding of the tools in question, by example or by annotated counterexample if necessary. |
||