We do agree. I'm referring to technical desing documents. whihc at best shuld be minimal if at all. A design document is useful *prior* to implementation, but not afterward.
At least in this kind of project. I'm sure building software for missle guidance systems or airline operation requies a different approach, but thats hardly relevant here ;o)
Besides, reading code is actually quicker (and weill certainly be a true system description).
Ok, I'll accept that in an ideal world, with infinite resources that can work at the speed of light, then having perfectly matched documents is good.
But as thats not the case, whats the point of aimn at the unattainable, better to work with human nature and circumstance?
