They are a form of documentation, but remember that documentation is in the eye of the beholder....

• For some, self documenting code is enough. But that assumes a level of technical detail as the customer.

• For those looking at source code but with less technical expertise, comments could be ok. But that assumes someone is looking at the source code.

• If you're technical, but lacking the time to read all the source code, a technical manual could be what's required.

• An if the user lacks technical skills, but just needs to know what is happening, user documentation is what's needed.

So the real question is who is your customer? If you are, then self documenting code or comments is enough. If it's for someone else, you might want to broaden how you document.

They are a form of documentation, but remember that documentation is in the eye of the beholder....

• For some, self documenting code is enough. But that assumes a level of technical detail as the customer. We should be careful thinking that this is enough, because our ego may tell us "It is obvious what this code is doing" but time can prove otherwise. It also assumes you know in advance the skills of the reader.

• For those looking at source code but with less technical expertise, comments could be ok. But that assumes someone is looking at the source code.

• If you're technical, but lacking the time to read all the source code, a technical manual could be what's required.

• An if the user lacks technical skills, but just needs to know what is happening, user documentation is what's needed.

So the real question is who is your customer? If you are, then self documenting code or comments is enough. If it's for someone else, you might want to broaden how you document.