Timeline for Checklist for how to write a good Code Review question
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2018 at 19:32 | comment | added | Simon Forsberg Mod | @greybeard Sad to see the original gone, thanks for finding it on the web archive | |
| Nov 13, 2018 at 19:32 | history | edited | Simon ForsbergMod | CC BY-SA 4.0 |
added 42 characters in body
|
| Nov 13, 2018 at 12:05 | comment | added | greybeard | (eating elphants on web archive.) | |
| Jul 22, 2017 at 19:50 | comment | added | Simon Forsberg Mod | Also see this answer by 200_success for information to add in the question. | |
| Aug 25, 2016 at 21:45 | history | edited | Mathieu GuindonMod | CC BY-SA 3.0 |
clumsily clarified the "Have you stripped your code from context" part
|
| Jan 6, 2016 at 15:42 | comment | added | Ethan Bierlein | I remember coming up with something like this quite a while ago, but this is much better. +1 :) | |
| Jan 6, 2016 at 13:42 | comment | added | Simon Forsberg Mod | @itsbruce Indeed. Just moved the usage + example input/output a lot higher up and added a note about edge-cases there. | |
| Jan 6, 2016 at 13:40 | history | edited | Simon ForsbergMod | CC BY-SA 3.0 |
added 11 characters in body
|
| Jan 6, 2016 at 13:39 | comment | added | itsbruce | Can't stress the example inputs and outputs enough. The examples should include edge conditions if possible (e.g. empty list passed in to a sort/search function). | |
| Jan 6, 2016 at 13:26 | history | answered | Simon ForsbergMod | CC BY-SA 3.0 |