Timeline for How can I be a nice reviewer?
Current License: CC BY-SA 3.0
15 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/
|
|
| Aug 3, 2016 at 14:33 | answer | added | pacmaninbwMod | timeline score: 0 | |
| Jul 11, 2015 at 3:44 | history | edited | JamalMod | CC BY-SA 3.0 |
edited body; edited tags; edited title
|
| Oct 22, 2014 at 11:24 | vote | accept | Pimgd | ||
| Sep 24, 2014 at 11:02 | comment | added | Nobody moving away from SE | I think I have the same problem but reading your title I ask myself: Is our goal to be nice or to be helpful? In most cases both is possible but when in conflict I would opt for the latter. | |
| Sep 19, 2014 at 10:09 | comment | added | JaDogg | Interesting, I think good answers don't have to be nice | |
| Sep 19, 2014 at 0:14 | history | tweeted | twitter.com/#!/StackCodeReview/status/512756502424088576 | ||
| Sep 18, 2014 at 20:07 | answer | added | Gareth Rees | timeline score: 27 | |
| Sep 18, 2014 at 16:47 | history | edited | Pimgd | CC BY-SA 3.0 |
code highlighing for 5 characters of code
|
| Sep 18, 2014 at 16:02 | comment | added | Ingo Bürk | Honestly, I don't think this is too harsh. If this is what you'd do – and I get that feeling a lot as well – why not say it that way? Just make sure you don't leave it with that and add some constructive insights on why it is so bad. | |
| Sep 18, 2014 at 15:49 | comment | added | RubberDuck | Related: meta.codereview.stackexchange.com/a/992/41243 | |
| Sep 18, 2014 at 15:45 | answer | added | Phrancis | timeline score: 20 | |
| Sep 18, 2014 at 15:38 | answer | added | rolflMod | timeline score: 33 | |
| Sep 18, 2014 at 15:19 | history | edited | rolflMod | CC BY-SA 3.0 |
tags, and context.
|
| Sep 18, 2014 at 15:15 | history | asked | Pimgd | CC BY-SA 3.0 |