In addition, @PhiNotPi 's wonderful answer, I think we need more strict guidelines on how code-trolling questions should be written. Perhaps these as a few starting requirements? (Some of these may already exist as criteria)

• Novelty - A question or topic should not be repeated unless there is a significant difference in interpretation. I.E. Answers to a previous question should not be able to be copy-pasted into the new question with only minor modifications.
• Clear Winner - There should be clear and simple rules explaining how a winner should be determined. If popularity-contest is applied, there should be a clear indication of what qualities make a good answer.
• A statement of what can and cannot be accepted. While each question may warrant variations, Here are a few examples:
  • No trivial solutions, like print("the code");
  • No malicious code, like rm -rf /
• Difficulty - There should be at least some challenge. A question asking to print a string backwards is not enough of a challenge to be remotely puzzling.
• Open to interpretation - The question should be somewhat vague, or allowing for (possibly deliberate) misinterpretation of what the OP wanted.