"There isn't any documentation," replied the business guy who had created the idea and written the checks to the programmer This is so vague, that it borders o

"There isn't any documentation," replied the business guy who had created the idea and written the checks to the programmer This is so vague, that it borders on absurd as a case of point. A counter could be levied by this example that many times the business sees no value in documentation, and is in a rapid cycle to get a first version out the door and is leaning on the developer to get it out the door. As a developer who is being contracted, he is familiar with the source so documentation is not critical for him to understand or maintain the system. It not until something goes wrong and the business is looking to sever their relationship with said developer, that documentation becomes important and it is always the developers fault if it is not done. If the business did not pay for documentation then they have no valid expectation that they should receive documentation. Conversely, the developer should stress the importance of paying the developer to document the system and help them understand the pitfalls of not having the system documented. The if I get hit by a bus speech.