And now that the code is working "terrific", whatever motivation was there to comment it, would have vanished!!

Do not worry, when "that little glitch" or "that added customer request" show up you will spend hours upon hours commenting it in order to understand what you, yourself, wrote.
In the development phase there is very little need for commenting because all is fresh in your mind, but you will have to come back to the code some day (if you are still employed) and the the defecation hit the rotary oscillator.

The sad thing is that when you can easily comment (while developing) the need is the least, when you need the comments (enchancing or fixing) the ability is the least.

It is a common misconception that you are to comment for other peoples benefit, try understanding a piece of uncommented code when you are asked to modify it a year or two later yourself.

Erik

PS whoever said that "C" was self-documenting should be executed at dawn.