125
votes
Things to avoid when writing challenges
Cumbersome I/O formats
Generally, allow flexible input and output formats. People want to write code to do your task of, say, composing permutations, not reading/writing numbers in a particular ...
- 144k
100
votes
Default for Code Golf: Input/Output methods
Programs may output by displaying it on screen.
This makes it possible to use languages like Vim script that can't print output directly to stdout.
Example from this challenge:
...
- 186
95
votes
Loopholes that are forbidden by default
Using a non-free language on a Cops and Robbers challenge
Most (currently all) cops and robbers challenges consist of two parts:
A cop submission, where a user posts some secret property of a ...
85
votes
Things to avoid when writing challenges
Rules inferred from test cases
Test cases are examples for people to check their understanding of the spec and the correctness of their code. They should not replace an explanation of how the output ...
- 144k
82
votes
Default for Code Golf: Input/Output methods
Functions may take multiple arguments via currying
For some functional programming languages like Haskell this is actually necessary, because only single-argument functions exist and functions with ...
79
votes
Default for Code Golf: Input/Output methods
The contents of the tape post-execution may be used as a Turing machine's output
- 11.9k
79
votes
Things to avoid when writing challenges
Making assumptions about language features
Unless you're writing a language-specific challenge, avoid terms specific to some class of languages, because these might not make sense for other languages ...
- 144k
75
votes
Things to avoid when writing challenges
Bonuses in code golf
Digital Trauma wrote an answer about this, but I have harsher views on bonuses, so I'm posting to let people vote separately.
Bonuses in code golf say things like "-30% of your ...
- 144k
75
votes
Things to avoid when writing challenges
Changing the challenge in the comments
If something was unspecified in your challenge, or if you've decided to make a change to the challenge (Such as to close a loophole), don't just leave a comment....
- 42k
74
votes
Things to avoid when writing challenges
Do X without Y
This isn't always bad, but it's been a particular trap for beginners, so be careful.
In the past, there were popular questions about doing a simple task but with the obvious method ...
- 144k
71
votes
Things to avoid when writing challenges
Explicitly disallowing or disadvantaging arbitrary (classes of) languages
This has become much rarer recently, but the occasional challenge by a new user still includes it, so here as an answer to ...
- 196k
66
votes
Let's allow newer languages/versions for older challenges
Trust the community and add a standard loophole
I think the community can handle the add-a-builtin problem (I may be very wrong). I think that if someone adds a feature to their language that is ...
- 13.8k
63
votes
Things to avoid when writing challenges
Putting test cases in a hard to use format
Supplying test cases is always a good idea, but people are more likely to use them (and thus have better tested code) if they can easily be copied and pasted ...
- 89.3k
62
votes
Loopholes that are forbidden by default
Abusing native number types to trivialize a problem
It is common practice to restrict challenges to cases where input, output and/or intermediate values of the algorithm of choice fit into the ...
59
votes
Things to avoid when writing challenges
Requiring minimum scores
In short, don't post a code golf that says "Your code has to be shorter than 100 bytes" (the same applies to any other winning criterion). The usual motivation is that the ...
- 196k
59
votes
Accepted
When can APL characters be counted as 1 byte each?
GNU APL and ngn/apl use UTF-8, so use a byte counting tool.
NARS2000 only uses UCS-2, so 2 bytes per character.
IBM's APL2 is the only modern APL that natively supports APL EBCDIC, so 1 byte per ...
- 29.9k
58
votes
Default for Code Golf: Input/Output methods
For stack-based languages, function's input may be pushed to the stack before calling
Stack-based languages may assume that the input for their function is automatically pushed to the stack.
- 11.2k
57
votes
Things to avoid when writing challenges
Chameleon challenges
Chameleon challenges look like they're about one thing but are really about another. In doing the challenge, most of the effort is spent on something peripheral. Fix this by ...
- 144k
52
votes
Things to avoid when writing challenges
Non-observable program requirements
The validity of a program should depend on things that can be observed when the program is treated as a black box. Examples are data written to standard output or ...
- 31.3k
51
votes
Default for Code Golf: Input/Output methods
Where applicable, Turing machines supporting multiple halt states may also output via their halt state
This is essentially equivalent to programs outputting via their exit code.
- 11.9k
51
votes
Things to avoid when writing challenges
Don't allow / ask for different things in languages with different capabilities
Don't write specs like "Do X. If your language doesn't support X, you can do Y instead". Examples are:
Do some math in ...
- 35.8k
50
votes
Default for Code Golf: Input/Output methods
Input for Turing machines may be written to the tape pre-execution
The read-write head should start on the leftmost cell of the portion of the tape containing the input.
- 11.9k
46
votes
What are programming languages?
We're asking the wrong question
We're having the XY problem. The question is really, "What formats should we allow in answers?" For this purpose, I think that markup languages and limited output ...
- 144k
45
votes
Things to avoid when writing challenges
"Ideally, your code will..."
Avoid recommended features in your spec. If it's not mandatory, answers won't do it. The goal is to write the shortest/fastest/winningest code that still satisfies the ...
- 144k
44
votes
Things to avoid when writing challenges
Arbitrarily overriding the defaults
The default code formats, input/output methods, and other defaults are a product of community thought and discussion. Don't change them just because you feel like ...
- 144k
44
votes
Things to avoid when writing challenges
Saying you should produce one or several outputs randomly without further specification
One random output
Say someone writes a challenge about generating a labyrinth of a given size (width and height) ...
- 104k
43
votes
Things to avoid when writing challenges
Requiring the use of unnecessarily "complicated" number types
A large proportion of our challenges deal with numbers, or lists of numbers. An important consideration is always what sort of numbers ...
- 196k
Only top scored, non community-wiki answers of a minimum length are eligible