When I'm working on my own projects, I usually prototype the documentation before starting coding the prototype. Once I have something sort-of working I write the full documentation and then write the full code.
I find that writing the full program documentation has many of the advantages of writing a full design spec in that it forces one to consider many details of usage and implementation but a) is actually useful in its own right and b) takes a heck of a lot less time.
no subject
I find that writing the full program documentation has many of the advantages of writing a full design spec in that it forces one to consider many details of usage and implementation but a) is actually useful in its own right and b) takes a heck of a lot less time.