I am not really tuned in to test driven development yet, although I'vewritten some programs that way (and found them quite valuable). As aresult, I have some weaknesses, some TDD things that I just haven'tacclimatized to yet.One of them is mock objects, specifically mock versions of complexobjects; I don't like them and thus I don't use them. In trying tounderstand my dislike of them, I think that they seem too complexand fragile for at

There is a certain school of thought in system documentation thatbelieves, to stereotype things, that there is no such thing as being tooexplicit or having too many examples. Much of Sun's Solaris documentationmakes a great example for this school.

Unfortunately, these people are wrong. There is such a thing as toomuch documentation, because having too much has a number of problems:

• your documentation becomes less and less readable, as the importantthings are buried under a flood of examples, cross references,and low

Here's an issue that I ran into recently: from version 1.4.20 onwards,lighttpd has stopped passing stderr to CGI processes, should onebe peculiar enough to run CGIs on lighttpd ( which can be done ). If you need error logging from your CGIs, you will haveto roll something on your own.

(Fedora 10 has lighttpd 1.4.22 and so is affected by this.)

There is a bug report for this, but I don't know