I can't help it, I always get the mental image of hands clapping sarcastically when I see something like that.

In my experience refactoring lots and lots of crappy code left by devs long gone, a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them. If the code doesn't have informative names and clear separation of concern, chances are a comment won't help because the dev didn't really know what they did that worked in the first place.

Comments should only be used to describe stuff that’s otherwise difficult to convey with code.

I write a lot of fairly simple scripts in Bash and PowerShell that should be easily understood by anybody else with moderate experience in the language, but I leave a lot of obvious comments because my coworkers don't write any code and are extremely skittish about my automations. I add them basically to quell their fears.

I'd rather teach people to comment well through my reviews. Much easier to understand two lines of well written function description in English than 20 lines of code.