I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.
I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.
I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.
I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.
I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.
I'd like to back up The problem with sandboxes, and a proposed solution.
Let's kill the sandbox
...
But, aren't we a Stack Exchange site? The entire network was designed so that there is no need for a sandbox. Is there not editing and closing? Questions don't have to be perfect immediately on posting; if you see a minor problem, just edit the post! Comment for major problems, and close unrecoverable challenges.
Are you starting to notice something? This is exactly what other Stack Exchange sites do!
(emphasis added after all emphasis removed)
We don't need such an elaborate solution. Just work out your questions beforehand (in a text editor / paste into a text editor), then post. Any problems can be solved in a short amount of time afterwards.
I used this method for the most recent challenges of mine:
Both challenges turned out fine. There were a couple mistakes that I fixed within the first day of posting.
For challenges that need more working out beforehand, I recommend using the chatroom designated for this. Usually, you don't need to post the whole challenge, just the idea and the possible problems. Then, discuss it with fellow codegolfers. I've found that this method, combined with the previous one works pretty well.
However, sometimes, you might only have an idea, but don't know how to create something from that. Use the chat. But if you need even more help, the current sandbox style works well. If you follow the other parts of this question, the sandbox will get less posts anyways.