# How to fix a poorly constructed question that you are the author of

I would like to know what the common practice is for revamping problems that were not constructed properly the first time.

The first(and only) code-golf puzzle I made was The struggling college student's GPA Calculator. I put the question into the sandbox and received a few feedback items, but being new to the site, I didn't structure the question in the way I would now. At the time of writing the question, I did not know that adding a lot of requirements(such as the rounding requirement and the I/O requirements) would lead to people disliking and not answering the question.

Does the site have any protocol for fixing questions like these, to allow more answers and more people to participate? Just opening up a new, better formatted question seems like it will get marked as a dupe.

• If it doesn't change the challenge too much you can generally change things like i/o and rounding. – Rɪᴋᴇʀ Jan 10 '18 at 21:41
• Despite my answer, your linked question does like 70% of what I mentioned. Keep asking stuff like that in the sandbox and you'll do great man/ma'am. – Magic Octopus Urn Jan 10 '18 at 21:50

# Sandbox 100% of your Posts

Sandboxing your posts is the best way to get attention to the flaws of your question, if you don't get a response within 12 hours, try the following:

• Post a link to your sandbox in The Nineteenth Byte, more experienced users often use this as a forum and will be glad to help (this is also where new sandbox posts / meta posts / regular posts appear).
• Make an edit to your sandbox post to bump it back to the top (do not abuse this, abuse The Nineteenth Byte before doing this).

# Recovering Outside of the Sandbox

If you happen to make a post that made it through sandbox, to the main site, and it is not well received (E.G. 3 downvotes in 2 minutes):

• Remove the post before it gets answers (once it has answers it is considered rude to remove).
• Or, ask in the comment section what can be done to fix it.

# General Guidelines (My Personal Opinion)

• Bullet points: nobody wants to read a paragraph in your challenge.
• Sections: Turn your post into multiple sections, some common ones I use are
• "Background": Tell the user the backstory and link to a Wikipedia or OEIS.
• 1-4 sentences MAXIMUM on the story behind why this challenge is neat.
• "Formal Definition": Tell the user the variables of the challenge, for example if your challenge takes 2 integers and outputs a list...
• Given n and m, where n is the number of bananas and m is the number of angry beavers, calculate the list of angry bananas b.
• "Examples": Give the inputs and their corresponding outputs.
• Hit base cases, hit edge cases and hit weird cases.
• If you have a rule that is odd, make sure that rule is hit by an example.
• "Rules": Define a rules section, I recommend keeping track of the common rules seen around the site.
• +1 for Given n and m, where n is the number of bananas and m is the number of angry beavers, calculate the list of angry bananas b.. On a more serious note, the advice to answer challenges as well is fantastic. Nothing helps you inherently know what to avoid like running into obnoxious restrictions in other challenges. – James Jan 10 '18 at 21:51