11 ms·

http://c2.com/cgi/wiki?TruckNumber http://c2.com/cgi/wiki?TruckNumber ............. Anyway, documentation is all well and good when it takes the form of a "ho

http://c2.com/cgi/wiki?TruckNumber http://c2.com/cgi/wiki?TruckNumber ............. Anyway, documentation is all well and good when it takes the form of a "how to". That seems to be what the author is getting at. But there's just nothing worse than reading or writing documentation that consists of proposed method signatures, object structures, or anything in any way related to UML.

pchristensen 19y ago
He's referring to business process documentation, which is different than code documentation. Coding (or design in general) is different than operations and can't be documented as precisely. It's the difference between "Here's what I did" and "Here's what to do"