News for hackers. Stuff that matters.
Re:Should I Comment My Code? The Case Against Code Comments by hellofunk on Thursday October 06, 2016 @08:49AM (#12651951)
No one wants to look through a lengthy git log to find the reason something was done to a particular block of code!
Re:Should I Comment My Code? The Case Against Code Comments by mattferderer on Thursday October 06, 2016 @09:16AM (#12652151)
Visual Studio Pro & up has a great feature that puts a tiny snippet of text above each class & method that says the last author, how many authors & how many changes have been done on that specific class or method. You can hover over this text and see a box with a scroll bar that shows you the commits & comments that changed the class or method.

I'm not sure if any other IDE or editors have this but I really love this feature as a method of documentation. I'm not saying it is the best method or the only method one should use, just a useful method that I wish more IDEs & editors had.

Re:Should I Comment My Code? The Case Against Code Comments by herbst on Thursday October 06, 2016 @09:30AM (#12652239)
I assume every damn editor out there has a plugin that makes this a complete non issue. I spend most of my time in a terminal anyway and know my way around it, i prefer it by far to comments, also because of the metadata like dates and authors which rarely is found in comments.
Re:Should I Comment My Code? The Case Against Code Comments by michael_h on Thursday October 06, 2016 @09:43AM (#12652348)
Half of the time, when I look at the git blame for a certain line, I get: 'whitespace-only change'