Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Comments on Posting guidelines modifications

Parent

Posting guidelines modifications

+9
−0

Currently, the posting guidelines for Code Golf are the defaults on Codidact.

Posting Tips: ¶ Your title should be a one sentence summary of your question. ¶ Break different topics up into paragraphs. Multiple paragraphs are easier to read than a wall of text. ¶ Use clear, simple language. Be specific. ¶ Reread your post before saving (preferably out loud) and rewrite anything that sounds awkward. ¶ Give context for your question. Tell us what you're trying to do and why. ¶ Tell us what you've already tried. ¶ Don't provide irrelevant information; it's a distractor from the question you want answered.

The pre existing guidelines on SE are the following:

Is your question a programming puzzle or code golf challenge? ¶ All challenge question on this site should have: ¶ 1. A clear specification of what constitutes a correct submission, so that it is possible to indisputably decide whether an entry is valid or not. Test cases are highly encouraged. ¶ 2. An objective primary winning criterion, so that it is possible to indisputably decide which entry should win. ¶ Please follow  astandard template and post first in the meta Sandbox for feedback. ¶ If your question is about this website, ask it on meta instead.

The main points of discussion are:

  • What would we like to add to the guidelines?
  • What would we like to modify in the guidelines?
  • Which existing/to be created meta posts should we reference in the guidelines?

This needs to be decided for each topic(each topic can be modified idividually), so please state which section you are talking about.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (2 comments)
Post
+4
−0

Since no one has posited anything yet...

I think everything but the last three bullets can be kept. Other than that, we could add in the tips about challenge specifications.

Challenges

Posting Tips

  • Your title should be a one sentence summary of your question.
  • Break different topics up into paragraphs. Multiple paragraphs are easier to read than a wall of text.
  • Use clear, simple language. Be specific.
  • Reread your post before saving (preferably out loud) and rewrite anything that sounds awkward.
  • Challenges should have a clear specification, with which entries can objectively be said to be valid.
  • Including test cases and an example (un-golfed) solution is encouraged.
  • Challenges should also have objective winning criteria.
  • If you are unsure about your challenge, please post in the Sandbox before release.

Sandbox

Basically the same thing except for the last line

Posting Tips

  • Your title should be a one sentence summary of your question.
  • Break different topics up into paragraphs. Multiple paragraphs are easier to read than a wall of text.
  • Use clear, simple language. Be specific.
  • Reread your post before saving (preferably out loud) and rewrite anything that sounds awkward.
  • Challenges should have a clear specification, with which entries can objectively be said to be valid.
  • Including test cases and an example (un-golfed) solution is encouraged.
  • Challenges should also have objective winning criteria.
  • Try to note down specific questions you have instead of asking for blanket feedback.
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

About test cases (1 comment)
About test cases
user‭ wrote over 3 years ago

I would say that for code-golf and code-bowling questions, including test cases should be mandatory, not just encouraged. On the other hand, C&R doesn't really need them.