Timeline for In 2014, how quickly, on average, are questions of popular languages answered on Code Review?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2014 at 18:00 | comment | added | Jamal Mod | @jt0dd: That's also why I sometimes refrain from going all-out on a review. I usually leave some things out so that there's still room for further answers. As for "looks good" answers, they must explain the reasoning behind this (though of course they can still be wrong). Answers that simply say "looks good" are subject to deletion as they really don't say much. | |
| Jul 20, 2014 at 17:58 | comment | added | user73428 | All of that noted and agreed with, I think there's one really powerful thing that reviewers seem to be forgetting here. People aren't necessarily asking you to dissect every ounce of their code. I think it would improve the site's morale, especially in the area of answer-speed, if all reviewers would make a habit of saying that the code looks good, make a general note why, and let that be an answer - askers have no problem with that, and they'll feel much better about coming back to the site. | |
| Jul 20, 2014 at 17:52 | history | answered | JamalMod | CC BY-SA 3.0 |