Timeline for Posting code to check a box
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:41 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
|
|
| Mar 16, 2017 at 16:03 | history | edited | CommunityBot |
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
|
|
| Jan 4, 2015 at 17:53 | vote | accept | Ben Aaronson | ||
| Jan 4, 2015 at 15:03 | comment | added | RubberDuck | @BenAaronson I would argue that questions like these fail the "Do I want feedback about any and all facets of the code?" test. Your second point is much harder to deal with. Unfortunately, there's not much we can do other than set a good example for others to follow. | |
| Jan 4, 2015 at 14:51 | comment | added | Ben Aaronson | Thanks for the answer! I think there are two issues that make these approaches less effective than they could be: 1. By posting code, the question does check all the boxes to be correctly within the scope of this site. So the line will always be blurred about whether closing/migrating the question which is apparently technically okay for this site is actually correct. 2. As I mentioned, if the real question is sufficiently interesting, often an answerer will actually want to answer it, so they have no reason to pick one of these three options | |
| Jan 4, 2015 at 13:27 | history | answered | RubberDuck | CC BY-SA 3.0 |