It was thus said that the Great Toby Thain once stated:
On 21/11/11 1:03 AM, Sean Conner wrote:
And yes, the project I've been working on
is working; it's now in
production and frankly, no bugs have been found---or rather, yes, bugs
*have* been found, but on the vendor's network that were never documented
nor mentioned to us, and thus, we had to work around those particular
issues.
Where did you write down all the information about those bugs and the
workarounds, or are you carrying it in your head?
I'm in the QA department, where I get to break the code our company writes
(documentation of the actual spec is done in another department). But I did
see reference to it in the revision log (we use SVN). In fact, I found it
easier to track the code through the revision logs than the actual source
code or documentation itself ("Oh, I see M added a new bit field to this
structure, I best update the testing tool to support that").
If you still doubt the Siamese connection between the
ability to write
well and the ability to code well, then please read The Elements of
Programming Style before we continue this discussion.
So, how many people here have done any literate programming?
-spc (Doesn't seem like many ... )