Timeline for Is code ever clean enough? - Can there be too many follow-up questions?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2017 at 15:46 | history | edited | CommunityBot | replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/ | |
| Mar 16, 2017 at 15:46 | history | edited | CommunityBot | replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/ | |
| Mar 16, 2017 at 15:46 | history | edited | CommunityBot | replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/ | |
| Oct 6, 2015 at 1:21 | history | tweeted | twitter.com/StackCodeReview/status/651205549661384709 | ||
| Oct 5, 2015 at 18:16 | answer | added | janosMod | timeline score: 25 | |
| Oct 5, 2015 at 16:31 | comment | added | Maroloccio | Simon, all we have is a UI problem, I think. If we had a commit stream like in GitHub, comments could follow the commits and all would be good. Code Review applied to a particular "point in time". | |
| Oct 5, 2015 at 16:03 | comment | added | Simon Forsberg Mod | @Maroloccio You say "choose a hint (among the many)", but in your case there was mostly only one hint (answer) to choose from. What you should aim at is improving the quality on your follow-up questions, see my answer here for more details. | |
| Oct 5, 2015 at 16:01 | comment | added | Simon Forsberg Mod | Another note: This question was inspired because of this question, which was the 5th in the series, but is meant to be applicable to all situations where multiple follow-ups are posted. | |
| Oct 5, 2015 at 11:11 | answer | added | Simon ForsbergMod | timeline score: 14 | |
| Oct 5, 2015 at 7:31 | answer | added | h.j.k. | timeline score: 13 | |
| Oct 4, 2015 at 20:53 | answer | added | Mathieu GuindonMod | timeline score: 15 | |
| Oct 4, 2015 at 20:15 | comment | added | Maroloccio | How do I do this on this site: post a question asking for some feedback, choose a hint (among the many) I really like and communicate I am interested in getting a review based on my code with that hint included, not the previous (now outdated) version? Maybe that's the question I should ask? At that point I don't personally see a reason to limit the amount of revisions, provided previous questions are closed and don't steal attention, but that's just me. | |
| Oct 4, 2015 at 20:03 | answer | added | Maroloccio | timeline score: 1 | |
| Oct 4, 2015 at 19:38 | answer | added | rolfl | timeline score: 15 | |
| Oct 4, 2015 at 19:28 | comment | added | Simon Forsberg Mod | Note: This is not intended as a duplicate of a previous question as this question is to establish a site policy, not a feature request. The previous question also seemed to touch on huge projects and not only pure follow-up questions (A follow-up question is a question which contains code that is a newer version of the code in a previously asked question) | |
| Oct 4, 2015 at 19:27 | history | asked | Simon ForsbergMod | CC BY-SA 3.0 |