I never comment my code

Good because comments lie

I only ever write comments if I need to explain why I wrote a certain bit of code. Mostly due to non-intuitive APIs 😅. And I only ever comment the smallest area because of the fact that "code changes, comments don't"

@mrstebo
Why don't you comment on big sections to separate them instead? That way you would have to change your comments not when changing details but the rough concept of your whole code.

@Niddam I think that would be called documentation...and we all know how much developers "love" to write documentation 😅

Always code like the next person maintaining your code is a psychopath & knows where you live.

Having no comments is ok reading code might lead us somewhere BUT having commented code all over the function makes me want to smash someone's face 😒😒😒

Good you better never do it.

FUCK YOU! - From all the poor bastards who are going to have to maintain your code months or years from now!

@codeRetard no, fuck him if he writes crappy code. The vast majority of your code shouldn't require comments for future maintainers to understand. If it does, you failed and wrote crappy code and that does suck.

@civel I so don't apply to that! what you said over there is so elitist, short sighted and wrong! Programming is an extension of the programmers logic and a series of best practices that the developers have acquired at the time of the development which is never all that it should be or complete! as a result, a proper commenting is required to explain the underlying reasons behind the used logic in the code. This is also a very good practice if your code manages to survive the test of technology age and then some poor bastard has to maintain the code 15 years down the line when your initial programming language is now a thing of the distant past! In the words of Kathy Sierra; Code as if the next person to maintain your code is a homicidal maniac who knows where you live! - That includes proper and sufficient commenting by the way!