Skip to main content
1 of 5
lamwaiman1988
  • 1.5k
  • 2
  • 16
  • 22

Why would company develop an atmosphere which discourage comment?

I was taught in University that we need to write comment for the programs. As I write the comments, I feel like having a better organization to understand what the programs are about.

However, I am in a company that most of the code I encounter doesn't have comment. Why would a programmer not writing comment, if there are any objective reasons? Do you think comment annoying when you read other's code? Neither do I write comment, and I think of some reasons: 1) because the program is easily understood by me. 2) My boss won't care how does my program get the job done. 3) Lacking a sense that somebody may pick up my program after I was gone.

The purpose of comment usually include explanation to the program, however, I found that in my company, comment was used to cover obsolete code instead. For example:

/* obsolete code */ new code 

What is your opinion towards commenting? Should we do it? Or does it depends on the situation?

lamwaiman1988
  • 1.5k
  • 2
  • 16
  • 22