Timeline for What is the best approach for inline code comments?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2012 at 1:55 | comment | added | wim | I agree 100% with your colleague | |
| Nov 8, 2012 at 0:24 | comment | added | Kirk Broadhurst | You need to improve your SCM process or toolset. And developers should be scared of changing every line regardless of how old it is. | |
| Nov 7, 2012 at 21:59 | comment | added | Robert Harvey | FWIW, where I work we use the third format (a basic comment) for ordinary descriptive comments, but are required to put author, date and time, and explanation when revisions to the code occur. However, there was dissent when this was implemented, for the reasons stated below. | |
| Nov 7, 2012 at 21:59 | history | edited | gnat | CC BY-SA 3.0 | added 2 characters in body |
| Nov 7, 2012 at 21:57 | history | tweeted | twitter.com/#!/StackProgrammer/status/266298436775706624 | ||
| Nov 7, 2012 at 21:48 | comment | added | Karl Bielefeldt | You really need to learn your SCM's blame/annotate/time-lapse feature. For each line in a file, it shows which revision that line was last changed in. No need to search through a long history. | |
| Nov 7, 2012 at 21:34 | history | edited | pdr | CC BY-SA 3.0 | Nope. Not "whom" in this case |
| S Nov 7, 2012 at 21:32 | history | suggested | Martijn Pieters | CC BY-SA 3.0 | Improve grammar and spelling. |
| Nov 7, 2012 at 21:25 | vote | accept | Diego Alvarez | ||
| Nov 7, 2012 at 21:24 | review | Suggested edits | |||
| S Nov 7, 2012 at 21:32 | |||||
| Nov 7, 2012 at 21:08 | review | First posts | |||
| Nov 7, 2012 at 21:24 | |||||
| Nov 7, 2012 at 20:58 | answer | added | Loki Astari | timeline score: 32 | |
| Nov 7, 2012 at 20:55 | answer | added | Axel | timeline score: 6 | |
| Nov 7, 2012 at 20:53 | history | asked | Diego Alvarez | CC BY-SA 3.0 |