True, but I work with HTML, CSS & JS. No need to compile

Ahh, then yes, in that case I do normally try to minimize the comments in my code. Good point!

I try to make things as clear as possible and comment when it might not be. I could comment more, but then again, all the comments add bytes and I try to save on bytes too (yes they should be removed for live code, but that’s not always feasible option) It’s a balance..

Many compilers will remove comments before compiling the code though. After all, they aren’t really needed in compiled binary code since it would just take up an unnecessary amount of room.

I see there are not too many female programmers around here to comment the article, though.

Unfortunately, there aren’t.

The same can be said of our teachers. While women usually write cleaner, more easy to understand code, including comments (which they always recommend), the men write more complex code, even more if they use something like C++, with all this geeky-prone syntax, and rarely they use any comment.

I see there are not too many female programmers around here to comment the article, though.

I’d have to say it also depends on what exactly you’re doing. If you’re working on a small project. That kind of cryptic code, without comment, will be faster to write, so it will be more time efficient, so there’s no point in wasting more time since it’s small. If you’re working on something big, you need to invest the comment time in it, since the project will probably have a long(er) life, and you’ll feel that investment when you revisit the code (yes, no headache! ).

That’s normally the rule of thumb that I go by as well. If I think I’m going to be coming back to the code down the road I’ll definitely put in comments. Sometimes I feel as though I over-comment on some things, but it doesn’t really hurt anything.

From what I’ve seen first hand, however, is that men and women tend to take a different approach at their coding. Men like to dive in and try to rapidly prototype something, whereas women like to think through how they are going to code what they’re after. That probably means that men have to go back and insert comments after they’re done, but women can probably insert them as they go. If you wait to insert your comments you’re probably less apt to do so when you’re done coding, because you’ll likely just think of it as a waste of time.

I’d have to say it also depends on what exactly you’re doing. If you’re working on a small project. That kind of cryptic code, without comment, will be faster to write, so it will be more time efficient, so there’s no point in wasting more time since it’s small. If you’re working on something big, you need to invest the comment time in it, since the project will probably have a long(er) life, and you’ll feel that investment when you revisit the code (yes, no headache! ).