Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Post History
In most Codidact communities, I will read the existing answers to a question before posting an answer of my own, to avoid repeating an existing answer. So far I have taken the same approach with th...
#1: Initial revision
Duplicate puzzle solutions
In most Codidact communities, I will read the existing answers to a question before posting an answer of my own, to avoid repeating an existing answer. So far I have taken the same approach with the Puzzles proposed community. I first try to solve the puzzle myself, then before posting an answer with the solution I have found, I check the existing answers to see if mine is different. I then only post if I have something new to add. An alternative approach would be to post an answer without looking at any of the hidden spoilers in the existing answers. This would give multiple answers with the same solution in many cases, but might also give different interesting explanations of the same solution. Which approach is taken by most people will probably depend on the example set by answers to existing puzzles. Without a discussion I suspect that the approach taken for other communities will be reflected here. Which approach would you prefer to be set as the example? Is there anything we could be doing to encourage one approach or the other?
