User talk:Waldorf: Difference between revisions
Content added Content deleted
(New page: ===Appropriate Tasks=== The recent turmoil concerning the ''structure'' task brings up a basic question. What are appropriate (and by inference, inappropriate) tasks for Rosetta Code? I...) |
(→Appropriate Tasks: Modularization) |
||
| Line 5: | Line 5: | ||
I agree that the ''structure'' task was ill-defined. Is it appropriate to define a new task to demonstrate language capabilities regarding specification of data representations? |
I agree that the ''structure'' task was ill-defined. Is it appropriate to define a new task to demonstrate language capabilities regarding specification of data representations? |
||
:I have no problem with exploring data representation. However, I firmly believe that tasks need to be modularized. A task that explores something needs to be created in such a way that prevents it from hindering the completion of other portions of the task. In practice, this means that a task needs to focus on as few things as possible. A task that focuses on data representation needs to be about data representation. |
|||
: |
|||
:Modularization is important because we need article titles to be representative of what the article is about. An article named "Custom data types" is not a good name for an article about sharing data between multiple languages, while "Share data between C and another language" would be. --[[User:Short Circuit|Short Circuit]] 15:44, 26 February 2007 (EST) |
|||