I do as a way to self-document the code. Many people who I have worked with love this because the code is easier to read, easier to understand, and becomes more maintainable. Just my two cents.
I did some programming for a civil engineering firm, where long, descriptive variable names were also important for making code easier to read and understand.
In this case, it was necessary because the code would have to be reviewed by others to pass QC.
Its not just for other developers (when I revisit something I've written months/years ago). But yeah, when I have to review code with Testing/QA, who aren't full time developers, it makes it much easier to step them through what is being done.
--
ps: especially since I'm always sparse on comments...
This. The general rule I have my teams follow is that I should be able to jump into the middle of a bit of code and understand what all the variables are and the methods do etc from their names. If you do this, then you'll find the amount of inline comments you need is drastically reduced, because you're basically saying the same thing in the comments that the variable and method names tell you.
Comments
I do as a way to self-document the code. Many people who I have worked with love this because the code is easier to read, easier to understand, and becomes more maintainable. Just my two cents.
I did some programming for a civil engineering firm, where long, descriptive variable names were also important for making code easier to read and understand.
In this case, it was necessary because the code would have to be reviewed by others to pass QC.
Just my two cents, added to yours, to make four.
$0.06
Its not just for other developers (when I revisit something I've written months/years ago). But yeah, when I have to review code with Testing/QA, who aren't full time developers, it makes it much easier to step them through what is being done.
-- ps: especially since I'm always sparse on comments...
This. The general rule I have my teams follow is that I should be able to jump into the middle of a bit of code and understand what all the variables are and the methods do etc from their names. If you do this, then you'll find the amount of inline comments you need is drastically reduced, because you're basically saying the same thing in the comments that the variable and method names tell you.