   post if you hate to document
  I just finished writing some code I want to publish, and now I'm documenting it. Since documenting your code is so boring, I decided to stop and post this meaningless thread here.   
  Actually, I find documenting is quite useful. I notice that you clearly delineated between "writing some code" and "now I'm documenting it". In my view, these two practices should actually be performed concurrently. This may be why you find it so boring -- it's a lot of work trying to remember what you were thinking when you wrote something 6 months ago.   ;  *doesn't post*   ;  I actually like documenting code. Not afterwards, but during coding - this way you always have a WORKING document that's reference to yourself and others.   ;  Documenting code for me (eg /// <summary> tags) is good.Documenting my applications for end users is bad.   ;  I actually tend to do a LOT of my documentation before even writing the bulk of my code.  Putting together the framework and classes and just documenting the intended functionality where appropriate, then going back and actually writing the code.  Adjustments to the framework happen quite frequently doing this, and such adjustments are considerably easier to make before the meat of the code is put in place.   ;  Personally, I don't document. I do write comments occasionally, but IME I'm the only one that can follow my code even with the comments I write. I try to write at least a line of comment for each function (ie "SetValue assigns Value to FieldName and returns true; returns false if the field doesn't exist"), but that is about the only regular commenting I do and it doesn't seem to really help anybody.   ;  I like commenting my code, but I do hate documenting code.  I stick with it because I want people to document their libraries.   I divide the tasks between coding and documenting, because my comments usually are enough(I prefer a summery at the start) that documenting is really just formating my comments into a readable and searchable format.   ;  I tend to only doucment interfaces.  I find it keeps people focused on what they should be using.  If they want drill down into the details then they are forced to read the code and understand it.That doesnt' mean the code doesn't have comments, it just doesn't have the full blown doxygen comments associated with it.CHeersChris   ;  Documenting can be really annoying... Yesterday I had to write documentation for my particle system code, and there's like 60-70 different parameters I had to write about so it was mind numbingly tedious.The good thing about documentation though is exactly that it Doesn't require much brainpower. So if I'm tired after lots of coding, instead of doing something unproductive, I work on documentation.   