Talk:One-time pad: Difference between revisions

Content added Content deleted

Inline

Revision as of 01:24, 25 November 2014

Clarity

Hi, apart from the fact that a one-time pad is to be used, this task description does not give enough direction to produce examples that would be comparable, as too much is left unsaid.

You could implement something in a language, check it for the amount of time needed to produce your implementation, (too long and it may take time to gain interest), then the task description could be honed to produce similar and comparable implementations in other languages. (But try and refrain from stating "just follow language X" in the task description. --Paddy3118 (talk) 05:45, 18 November 2014 (UTC)

It didn't seem that urgent, to have a very detailed task-description up front, as well a solution.

After all, the task is not much more complicated as rot13/caesar/vignere etc.

With a broader scope, somebody might already have some solution ready, or suggestions / requirements to add.

But I haven't seen much discussion going on about tasks...

BTW, Rosetta Code:Village Pump/Suggest a programming task needs cleanup... --Hajo (talk) 20:35, 19 November 2014 (UTC)

Hi Hajo, the task description needs to be enough to allow people that don't know the subject to follow it and create comparable solutions. Sometimes it goes well, sometimes people with the best of intentions interpret the task description in a different way to produce non-comparable language examples - that is to be avoided and leads to discussion on talk pages and probably modification of the task description.

If the draft task starts with both a "tight" description and a first implementation then this helps it progress to full task status as it aids others in generating their examples. We need to set some standard for draft tasks to stop people from using them instead of the Rosetta Code:Village Pump/Suggest a programming task page which is where people with the idea for a task, but without the wherewithal to start a draft task with enough umph to propel it to full task status should add their ideas.

Oh, and yep - that task suggestion page probably does need a cleanup. I would not be surprised if some suggestions are available as tasks and so probably should have their (approximate) task match appended. --Paddy3118 (talk) 01:24, 25 November 2014 (UTC)

@@ Line 9: / Line 9: @@
 :But I haven't seen much discussion going on about tasks...
 :BTW, [[Rosetta Code:Village Pump/Suggest a programming task]] needs cleanup... --[[User:Hajo|Hajo]] ([[User talk:Hajo|talk]]) 20:35, 19 November 2014 (UTC)
+Hi Hajo, the task description needs to be enough to allow people that don't know the subject to follow it and create comparable solutions. Sometimes it goes well, sometimes people with the best of intentions interpret the task description in a different way to produce non-comparable language examples - that is to be avoided and leads to discussion on talk pages and probably modification of the task description.
+If the draft task starts with both a "tight" description and a first implementation then this helps it progress to full task status as it aids others in generating their examples. We need to set some standard for draft tasks to stop people from using them instead of the [[Rosetta Code:Village Pump/Suggest a programming task]] page which is where people with the idea for a task, but without the wherewithal to start a draft task with enough umph to propel it to full task status should add their ideas.
+Oh, and yep - that task suggestion page probably does need a cleanup. I would not be surprised if some suggestions are available as tasks and so probably should have their (approximate) task match appended. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 01:24, 25 November 2014 (UTC)