I get what they are talking about in that blog, but it reads more like a guide of what -not- to do, rather than saying why comments are bad. If you're commenting so much you have more comments than code: you're doing it wrong!
The main issue is that commenting code is very contextually subjective, so there is no "one size fits all" answer. My moniker is: "if it isn't blatantly obvious what I'm doing or more importantly -why- i'm doing it", provide a minor comment.
Show differencesHistory of post edits
#1Net Gnome
Posted 14 April 2012 - 01:07 PM
I get what they are talking about in that blog, but it reads more like a guide of what -not- to do, rather than saying why comments are bad. If you're commenting so much you have more comments than code: you're doing it wrong!
The main issue is that commenting code is very contextually subjective, so there is no "one size fits all" answer. My moniker is: "if it isn't blatantly obvious what I'm doing", provide a minor comment.
The main issue is that commenting code is very contextually subjective, so there is no "one size fits all" answer. My moniker is: "if it isn't blatantly obvious what I'm doing", provide a minor comment.