2 ms·
The vast majority of the time, I'm writing comments for myself so that when I'm looking back on this same piece of code tomorrow, next week, next year, next dec
by wvenable 17y ago
The vast majority of the time, I'm writing comments for myself so that when I'm looking back on this same piece of code tomorrow, next week, next year, next decade, I can get myself into the same frame of mind. A comment on code I'm working on today isn't very useful. A comment on code I haven't looked at in 5 months and won't look at again for another 5 months is a lot more valuable. Very shortly I have to delve into some of my own code that's almost a decade old -- I hope I commented it well.
Given the authors resume, he might simply not have enough of his own old code to get the usefulness of comments.
- dbz 17y agoI do it for the exact same reason. I was asked to work on a project one time (small OS) and I was going to remake the core. The person had made it a couple months ago and had no idea what was what when I asked him about it. If he had just taken the time to write a comment here or there explaining some of the things, it would have been much easier than debugging the entire OS (which I had to do). The worst part was that he put in all of these extra "checks" and "lists" containing information each time programs would run (ect.) and they turned out to be completely useless and affected nothing. Anyways. My point is that a comment here or there on projects would help immensely. Especially if you may drop a certain part of a project and not maintain it for a period of more than a few days. Not all code is self explanatory.
- j_baker 17y agoFor those of you wondering where the link to my resume went, I've since removed it. I'm not saying that what wvenable is saying isn't reasonable. It's just that I'd rather be judged by whether my content is very good rather than by my resume.