This is a discussion about the rules. Actual rules can be found in https://codegolf.stackexchange.com/tags/code-trolling/info
The first ever question with code-trolling tag (I need a program where the user inputs an array of doubles and the program outputs the array sorted) has been a success and it seems reasonable to assume we will see more of these. It might be a bit early, but I hope to open a discussion on what the rules should be. Original rules:
Suppose that some lazy guy in StackOverflow or elsewhere, asks a homework give-me-dah-codez question. Your task is to give a code that works, but is still useless, severely frustrating the OP.
This could be achieved by:
- Deliberately misinterpreting the question and giving a code that clearly answers what the OP asked, but does something different than what he intended.
- Giving a code that runs in superexponential time or worse, when the trivial solution would be linear or better.
- Introducing something extremely unacceptable or unreasonable in the code that cannot be removed without throwing everything away, rendering the answer utter useless for the OP.
- Writing a code that is a direct and plain cheat on the question. Being a creative troll.
- Being evil.
In your answer, you should briefly explain what you are doing to troll the OP.
Further, we have one restriction: The chosen language should not be the sole reason to troll the lazy OP. Otherwise, you could just plainly encode the correct solution using brainfuck, golfscript or some language that is clearly a crazy, unexpected or unusual choice for the problem, but this would ruin the intention of this as everybody would do that. The intention is to write the homework in a language that the lazy OP might think acceptable, but still frustrate him.
To start the discussion I propose the following change:
- Not being evil. I understand evil as in
rm -rf /.
- A nice way to limit the
print "the sorted array"answers.