Any hard rule about this will slip quickly from "helpful convention" to "torturous ideology".
Use comments to explain why a piece of code is doing what it's doing. Or to help organize thoughts. Or to document public methods for tooltips. And do it consistently, unless that doesn't fit, then do something else.
But heaven's sake, please do inject jokes and humor into your comments. I distrust teams that are against this.
I write tutorials on my blog at www.lankydan.dev . During the day, I am a Platform Engineer at r3 where I work on Corda, an Open Source DLT/Blockchain Platform.
Any hard rule about this will slip quickly from "helpful convention" to "torturous ideology".
Use comments to explain why a piece of code is doing what it's doing. Or to help organize thoughts. Or to document public methods for tooltips. And do it consistently, unless that doesn't fit, then do something else.
But heaven's sake, please do inject jokes and humor into your comments. I distrust teams that are against this.
I misread the last paragraph the first time I read that which gave me a completely different impression of you 😄