Write out what the program is suppose to do, now how it does it. If the documents are for your own use, make them as detailed as you want. When you''re writting documents, you''ll think of things you might not of thought of right away. These things might affect the way your program works or is structured.

I''d make them almost as detailed as a flow chart. When you have docs like that, the coding will just be "filling in the blanks".

For instance: I recently wrote a quick program but I didn''t have very good documentation, just some notes. Later I wanted to add the ability to save out its data elements to a file. My program was using a lot of pointers and I didn''t have anyway to mark an element as unique, only by it''s memory address. Of course I couldn''t save that to disk so I had to change the structure of my program to include a unique ID on each element. I also had to add code to setup this ID when an element was created (which could be done in several different ways, for each of the 7 types of data I''m using)

E:cb woof!