The way I write code is like this:

 1. I write a comment for each future line of code (except for brackets and blank lines).
 1. I write the code under each such comment. In some of the cases where I write the code I encounter that I must write it somewhat differently and then I also change the corresponding comment, above it.

I then see value in leaving those comments where they are because when I read my own code then I can read the comments and not miss a line of code. The principal logic is described in spoken language in most of the cases. Saves me a lot of energy and I hope that it will for others, as well.

So, I'm not happy about removing comments. The fact that the code that follows a comment is easily understood makes little difference.

Granted, this style of commenting that I've just described supplies not an explanation of *why* any code is used, at all. And that may be as equally or more important comment information. I will begin, in cases where it would seem to me to be helpful, to add such type of *why* comments.