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
-
Understanding what code does is not the problem: https://dev.to/andreasklinger/...
-
Don't get me wrong man...... I use comments myself..... But I've seen comments as big as short stories and that got to me :P @SoulSkrix
-
akiroz4657yI don't write comments... I write documentation in markdown files explaining what the system does and how it works on a higher level.
Only exception is dirty hacks, in which case I'll leave a comment explaining why it's there and reference related issues.
When you have hundreds of source files, comments are pretty uselles IMO... -
The rule of thumb is, if a fellow programmer is able to figure out what your code does faster than he would reading a discription about it, then leave the comment out. Otherwise comment laconically. If your code is complex though, comment thoroughly.
-
Root825997y@cyberlord64 That is a very good way of explaining it. I'll have to remember that. Kudos!
-
I feel it's dependent upon how complex the code is, and if you're sharing the source or not. Sometimes leaving comments is a courtesy to others. I use comments a lot, however, I'm new to programming. Maybe with some more experience I'll feel differently, but right now comments are invaluable.
-
timothyferriss-3220dWhile good code should be self-documenting to a certain extent, comments can provide additional context that can't be easily gleaned from the code itself.
https://fnaf-game.io
Related Rants
Shouldn't be necessary if you just write understandable code xD..... Some people just write stories in between 2 lines of code....
undefined
comments
advice