Timeline for Are More Comments Better in High-Turnover Environments?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2024 at 1:10 | review | Close votes | |||
| Dec 19, 2024 at 3:01 | |||||
| Jun 4, 2012 at 16:21 | vote | accept | joshin4colours | ||
| Jun 1, 2012 at 16:35 | comment | added | joshin4colours | @Caleb Even if it wasn't clean and clear, do you really think smattering comments all over the place would help? Why not just write some documentation elsewhere with descriptions? | |
| Jun 1, 2012 at 14:02 | answer | added | Dave | timeline score: 0 | |
| Jun 1, 2012 at 6:48 | answer | added | tylerl | timeline score: 4 | |
| Jun 1, 2012 at 3:57 | comment | added | James Youngman | Lots of good suff in the existing answers. But just wanted to say that if there are now/few unit tests, invest the time in building tests, not comments, for the high turnover environment. If there is time left over for comments, add 'why' comments to both the code and the tests. | |
| Jun 1, 2012 at 3:34 | answer | added | Michael Durrant | timeline score: 5 | |
| Jun 1, 2012 at 2:49 | comment | added | Caleb | What do you think will happen when you move on to a different project or a different job and someone else has to maintain your code? Is your code really so clean and clear that someone else will easily understand what you were doing and why? | |
| Jun 1, 2012 at 2:15 | history | tweeted | twitter.com/#!/StackProgrammer/status/208381162576543745 | ||
| Jun 1, 2012 at 1:57 | answer | added | MathAttack | timeline score: 1 | |
| Jun 1, 2012 at 1:21 | answer | added | yannis | timeline score: 23 | |
| Jun 1, 2012 at 1:20 | answer | added | pdr | timeline score: 11 | |
| Jun 1, 2012 at 1:16 | answer | added | Oleksi | timeline score: 6 | |
| Jun 1, 2012 at 1:03 | history | asked | joshin4colours | CC BY-SA 3.0 |