I'm a programmer that hates to comment his code so I don't do it. Most programmers feel the same way. Basically the reason we don't do it is because we don't have to. I suspect the only way it will happen is if our code needs it to properly compile.
Changing, say, a function should prompt the IDE to somehow "tag" the associated comment so that you remember to check its accuracy, at the bare minimum. Other nice-to-haves would be having references to code, e.g., if you talk about variable x in your comment and then rename it, the comment reference should be updated.
You can feel the disdain for code commenting in the industry by looking at the anemic tool support for comments.
If you've been a developer for any length of time, I'm sure you will have encountered a situation where you've read some code, thought to yourself "wow, that's terrible, I'm going to change that". Then, several hours later, realised why it was done the way it was and actually, you can't really improve it after all. That is why we comment; to save the next person who enters the cave (and, if you're the kind of dev who spends several hours trying to understand something and doesn't retrospectively comment what you've found, then I'm afraid we can never be friends).
And please, don't assume the next person has the same knowledge of the system that you do.
Declare each variable and argument on separate lines, and add a one-liner comment next to each. If you are afraid that you will fall into comment verbosity hell, you can set up a rule to force yourself to use only single-line comments.