Skip to main content
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Code code:"if (foo != bar)"
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Saves in:saves
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with
Search options answers only not deleted user 20260

For clarification of rules that apply to challenges if not mentioned by the author

15 votes

Things to avoid when writing challenges

Parsing expressions In challenges dealing with algebraic expressions, don't make the golfer parse input strings like x^3-2x+1 or e^2^x, or to output in this form. This is cumbersome I/O that takes a l …
xnor's user avatar
  • 147k
4 votes

Default policy for output in decision problems

I'm for standardizing defaults in general, but I think we're not at that point for decision problem output. …
xnor's user avatar
  • 147k
20 votes

Things to avoid when writing challenges

Exceptional edge cases Don't require special behavior when the input is the empty list, the number 0, a negative length, etc. This makes for nasty surprises for solvers who worked on a solution only …
xnor's user avatar
  • 147k
37 votes

Things to avoid when writing challenges

Allowing standard loopholes in general Don't say "Standard loopholes are allowed". They ban silly things like making up a language where the solution is a single character or just printing the string …
Riker's user avatar
  • 7,850
10 votes

Defaults for word lists

We already have defaults for how to take input, so just use those. This includes reading from a file, STDIN, function input, etc. …
xnor's user avatar
  • 147k
16 votes

Things to avoid when writing challenges

Assuming you've addressed sandbox feedback When your challenge is in the sandbox and someone suggests a change or clarification, make sure your edit actually addresses their point. Too often the same …
xnor's user avatar
  • 147k
22 votes

Things to avoid when writing challenges

Using old challenges as a model Just because an old challenge did something doesn't mean yours should too. Many old challenges wouldn't pass muster nowadays. Don't be surprised if your challenge is d …
Community's user avatar
  • 1
5 votes

Things to avoid when writing challenges

Pure programming puzzles Despite our name, programming puzzles aren't generally welcome here. I'm talking about challenges where you're given a task with some impossible-seeming restrictions and must …
Community's user avatar
  • 1
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 ba …
Community's user avatar
  • 1
24 votes

Things to avoid when writing challenges

Narrow references Beware of challenge topics that tickle your fancy, but others won't appreciate. An in-joke among friends A reference to a movie you like A task from actual code you wrote A small …
xnor's user avatar
  • 147k
33 votes

Things to avoid when writing challenges

Patching out approaches On your challenge, someone posts a solution that's cheap and not at all what you intended. You have the option to change the rules, but do so very carefully as there's many pit …
Community's user avatar
  • 1
21 votes

Things to avoid when writing challenges

Tacked-on fixes If you clarify or modify your challenge after posting, don't just tack on a note to the end or to a list of bullet points. Edit in the change. It's confusing when the body of the ch …
Martin Ender's user avatar
59 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 bein …
Community's user avatar
  • 1
86 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 m …
Community's user avatar
  • 1
28 votes

Things to avoid when writing challenges

Popularity Contests Popularity contests, while allowed, are heavily disfavored by site culture. You're likely better off reworking your challenge to use an objective winning criterion that isn't vote …
Community's user avatar
  • 1

15 30 50 per page