For just about every case, I would have to agree with Ovid's thoughts on this subject. Particularly his point in the following:

Ugh! What the heck have I done? I took a simple, straightforward program, added three subroutines and several lines of code. Why the heck would I do something like that? What happened to laziness?

This is a trick question, as it isn't actually laziness we're seeing here. Larry calls this false laziness! Laziness isn't about always trying to do the least amount of work now -- laziness is about having the correct program design so that we don't end up rewriting the whole thing every time you need to add or modify a feature. Laziness is about saving time in the long run, which possibly may require spending some extra time up front.

The following is a direct quote from the Camel book, page 993:

Laziness
The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer. Also hense, this book.

I think Ovid does a fine job at expressing the intent of the Camel book, and more specifically, the 3 virtues of a good programmer, with his above thoughts. Two thumbs up!
-Eric