Timeline for Are More Comments Better in High-Turnover Environments?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2012 at 13:00 | comment | added | Michael Durrant | +1 Hi Yannis, yes that's a very good point. I agree. I also think that because code itself is a little more structured - has fixed names for certain things, simplest example - a function "to_string" has no ambiguity, must be called that, where as comments have absolutely zero structure or agreed upon terms kinda thing, that makes comments troublesome. Then again code can end up with a lot more 'spaghetti' then comments. Interesting. | |
| Jun 1, 2012 at 10:56 | comment | added | yannis | The issues you list are also issues for the code itself in a high turnover environment, not just the comments. That's... interesting ;) More of a people problem, than a code / comments problem. | |
| Jun 1, 2012 at 3:34 | history | answered | Michael Durrant | CC BY-SA 3.0 |