Timeline for "Open and closed doors" riddle
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2014 at 9:42 | vote | accept | Anirudh | ||
| Aug 28, 2014 at 17:31 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 23 characters in body
|
| Aug 28, 2014 at 12:09 | history | edited | Pimgd | CC BY-SA 3.0 |
formatting it a bit
|
| Aug 28, 2014 at 11:14 | answer | added | Anirban Nag 'tintinmj' | timeline score: 6 | |
| Aug 28, 2014 at 11:00 | history | tweeted | twitter.com/#!/StackCodeReview/status/504946624930799616 | ||
| Aug 28, 2014 at 10:57 | answer | added | rolfl | timeline score: 11 | |
| Aug 28, 2014 at 10:54 | answer | added | Pimgd | timeline score: 16 | |
| Aug 28, 2014 at 10:39 | answer | added | Simon Forsberg | timeline score: 10 | |
| Aug 28, 2014 at 10:20 | comment | added | rolfl | In general, people reviewing code will focus on those issues that are most broken in your code. If the style makes the function of the code hard to review, the style will be the focus of the review. If everything is perfect in your code, and the the only perceived issue is with your style, then again it will most likely be the target of the review. It is a good thing that your style is not completely horrible here, but nor is your code perfect. | |
| Aug 28, 2014 at 9:56 | history | asked | Anirudh | CC BY-SA 3.0 |