Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
asgs112755yWith caution, yeah. In essence, log only when necessary. Otherwise, critical messages become a few needles in haystack
-
@asgs Prolly right but dear god such comments are everywhere in the codebase and dont' seem to be related to anyhting specific and trust me.... got plenty of needles in the haystack :-)
Well it seems I won't get bored this week -
Comments... Should be used when necessary.
That's just bogus, irritating information which costs space, is confusing and completely dumb. -
The standard solution is to have different verbosity levels, usually configured via command line argument. From level 0 like no output, return code only to level X with full debug output. Default would be printing errors only, or success in absence of errors.
-
@Fast-Nop Yes, usually a good idea. However, do not add comments for the sake of comments. Especially when comments are misleading, the comment can have serious impact. :/
Related Rants
I cannot get my head around this comment
Does it mean write to console with "caution"? Or is it an obscure tribute to Dragonlance?
random
weirdcomments
puzzled
powershell