I've never seen a language's style guide recommend avoiding comments before
Of course everyone thinks they always write good clean code and therefore don't need comments to elaborate on what the heck is going on.<p>Unfortunately, having been doing this trade for 30+ years, I've found most people write crappy code in a hurry to try to hit some deadline based on incomplete requirements and confusing business rules.  A few precious comments stuck in there can help the next guy, months or years later, figure out what the heck your original intent was or why a block of code exists at all.<p>As I get older, I find it helps me remember what I was doing.<p>One of my software developer friends was fond of saying:  "the worst code I ever saw was my own!"<p>YES if your code is clean and elegant and well named and clear you don't need to explain anything in common language.<p>YES you should strive for such.<p>However, the REALITY is your code sucks and no one is going to  want to have to figure out what the heck you were doing.  A few comments would really help.<p>The next reality is that the typical developer may be literate in a dozen or more languages and the language du jour that you coded so elegantly in has fallen out of favor and no one remembers those dusty corners you so beautifully exploited to make something work.<p>Comments would help even more if you learn to use some basic grammar and spelling when you create your comments.  (It doesn't have to be literature, but try to make your comments as readable as you think your code is - please!)  Nothing will turn another developer off to trying to decipher your code than a few comments that make you look like a moron.<p>Style guides that eschew comments, IMO, are counterproductive.  They feed on the developer's ego and disregard reality.<p>Comments cost essentially nothing to add to your code and can save it from an early death and complete refactoring by the next guy who comes along.