[slotrans]

> I will completely forget why I wrote it that way.

This is the main reason for comments. The code can never tell you "why".

Code is inherently about "what" and "how". The "why" must be expressed in prose.

[Cthulhu_]

And the described use case - USB stuff with very specific exception - makes a strong case for literate programming, that is, more prose than code.

[lompad]

Does everything have to be pushed into a structure-prescribing set of rules?

Can't we just say "comments are useful here" without trying to make it into a case for $methodology?

[ninetyninenine]

Why not put the prose in the name of the function?

[SAI_Peregrinus]

Function names are limited. E.g. can't provide a circuit diagram of what you're controlling in a function name. But you can do that in a comment (either with ASCII art or an image link).