Comments are a skill in and of themselves, which a whole lot of people never master.
I remember two people who worked at a place where I was programming. The first
was a woman, freshly out of school who was taught that comments made the code.
So she dutifully wrote beautiful comments on the theory of what the function was
going to do, but also inline, especially for arcane things going on in an algorithm. All
nicely spaced, neat. A marvel to behold. Problem was, the code this person did
had some form of overflow condition (this was C) about every five lines, such that
I knew if I poked at the code from a higher layer I could cause problems. And did,
because I was trying to force the issue and have some kind of review go on.
The other person in the larger group was a 20ish male, who saw human interaction
largely through the eyes of TV, and gaming / nerd get-togethers. Hardly a bad person,
he just didn't seem to have humans around him when growing up (more than a trifle
odd, even now--I met him again for the first time in 20 years; the only change was
gray hair). He was one of the people I'd go to for help when I botched things, or
wanted comments on an idea I had. His code often worked the first time run, and
I'm not talking of little 10 line routines, but larger complex functions. His comments
were about the opposite of the code, both in terms of spelling, grammar, and that
ephemeral concept of how to communicate in general. Some sentences were
better read thinking of them as RPN, and others simply defied standard logic.
Comments that did survive that minimal test of English were often spelled in
novel ways, causing euqal parts of head scratching and laughter. But the code
I offer these two examples which while extremes, are examples that poke holes
in the idea that there is a common relationship between comments and code.
Certainly some people will fit that mold, but I think that more random than not.