Skip to main content
Post Closed as "Needs more focus" by Robert Harvey, gnat, Greg Burghardt, Thomas Owens
Question Protected by gnat
Rollback to Revision 1
Source Link
Robert Harvey
  • 200.7k
  • 55
  • 470
  • 683

junior developer here.

I am currently working alone on a web appsapplication for a big client of my company.

The I started last month. The client wants >at least 25% of comments in each of its software projects.

I checked the code of prev. apps.previous applications and here are my obs.observations :

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all gets'n'setsgetters and setters are commented
  • vvery few useful comments

It seems like devsdevelopers just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your adv.advice on this subsubject ? How should I handle the sitsituation ?

I am currently working alone on a web apps for a big client.

The client wants > 25% of comments in each of its software projects.

I checked the code of prev. apps. and here are my obs.

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all gets'n'sets are commented
  • v few useful comments

It seems like devs just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your adv. on this sub? How should I handle the sit?

junior developer here.

I am currently working alone on a web application for a big client of my company. I started last month. The client wants at least 25% of comments in each of its software projects.

I checked the code of previous applications and here are my observations :

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all getters and setters are commented
  • very few useful comments

It seems like developers just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your advice on this subject ? How should I handle the situation ?

reduced the number of characters to get the comment % up
Source Link
Ewan
  • 84.5k
  • 5
  • 91
  • 189

junior developer here.

I am currently working alone on a web applicationapps for a big client of my company. I started last month. The

The client wants at least> 25% of comments in each of its software projects.

I checked the code of previous applicationsprev. apps. and here are my observations :obs.

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all getters and settersgets'n'sets are commented
  • veryv few useful comments

It seems like developersdevs just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your adviceadv. on this subject sub? How should I handle the situation sit?

junior developer here.

I am currently working alone on a web application for a big client of my company. I started last month. The client wants at least 25% of comments in each of its software projects.

I checked the code of previous applications and here are my observations :

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all getters and setters are commented
  • very few useful comments

It seems like developers just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your advice on this subject ? How should I handle the situation ?

I am currently working alone on a web apps for a big client.

The client wants > 25% of comments in each of its software projects.

I checked the code of prev. apps. and here are my obs.

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all gets'n'sets are commented
  • v few useful comments

It seems like devs just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your adv. on this sub? How should I handle the sit?

Source Link
Robin_
  • 553
  • 1
  • 4
  • 9

My client wants 25% of comments in my current project, how to react?

junior developer here.

I am currently working alone on a web application for a big client of my company. I started last month. The client wants at least 25% of comments in each of its software projects.

I checked the code of previous applications and here are my observations :

  • each file begin with a comment block (package, date last updated, name of my company & copyright)
  • all variables are commented with their names
// nameOfCustomer public String nameOfCustomer 
  • all getters and setters are commented
  • very few useful comments

It seems like developers just place as much comments as they can to hit that 25% threshold, regardless of quality and usefulness. My company tells me that "we do it as the client wants it".

I did not speak directly with the client about this. Here are my arguments so far :

  • useless lines to read and to write (waste of time)
  • comments are sometimes not updated (source of confusion)
  • developers are less likely to use or trust real useful comments

What is your advice on this subject ? How should I handle the situation ?