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
-
Plus there are document web site builders based on the scanned code and basically comments
In python, Sphinx tool can generate documentation based on docstrings in Google style and other normal written pages in ReStructurizedText language -
Use variable names that explain themselves instead of letters, numbers, and/or abbreviations. Comment if you must but don't write essays.
Read Clean Code -
Document ONLY when you can’t express your intent through code.
Instead of comments:
Use meaningful variable names and method names and extract code blocks into methods like @atheist said.
Break down long call chains into multiple lines and assign intermediate values to variables which give meaning to the intermediate steps.
Don’t document just for the sake of documentation.
Don’t document based on some stupid rules like everything that is public or everything that is a method.
Automatically generated documentation is useless.
Learn to write self documenting code.
Related Rants
Any tips on how to properly document my code? I'm going to start my first internship soon so I need to learn it.
question
documentation