If you are in charge of reviewing someone's pull request and ensuring they adhere to specified company guidelines, you can do whatever your organization wants. Outside of that though, you lack the authority to tell programmers how many comments are too much. I too know how to write self-documenting code, but that doesn't mean your code should have no comments or shouldn't be liberally commented.
GP mentions that this is a textbook unnecessary comment and I would beware any textbook and professed expert that disagrees.
Whether a LLM coding model demonstrates understanding of unnecessary comments might be interesting, as would any differentiation in quality if my prompt asked for more or fewer lines of comments.
And I would beware any professed expert who has such a oversimplified heuristic of what makes a good engineer.
> Whether a LLM coding model demonstrates understanding of unnecessary comments might be interesting
I think it would be an interesting experiment, that sounds like a great idea for you to pursue. Make sure to sample a wide variety of models, and include a caveat that LLMs are not a source of truth regarding such matters, as they are simply providing probabilistic text completions based on prior training data.
