When you read software engineering books like Clean Code, they are generally heavily in favor of writing good comments. When you read programming books, like "

When you read software engineering books like Clean Code, they are generally heavily in favor of writing good comments. When you read programming books, like "Learn Language XYZ" books, there are generally no comments whatsoever because there is no need. Which makes sense in the scope of such books, but I think it accidentally sets a precedent for eschewing comments in the minds of many. But. Out in the "real world?" I'd say 90-95% of coders don't comment a damn thing. At least that has been my experience working in the industry since the 90s. Some coders are in the obnoxious and toxic "code should be self-explanatory" camp, which is objectively dumb. Code can't explain intent, such as business rules or weird shit you're doing to work around weird shit in external libraries or APIs or hardware bugs. A greater number of coders are of the mindset that inline comments are bad and that things should be explained in the commit message and/or pull request. This is more noble, but I think it is not nearly as practical as inline comments for a variety of reasons. Many coders also believe that comments make code harder to read. I find this baffling and dumb. Get a bigger monitor or get an editor that lets you collapse/hide comments with a keystroke.