The reason for "more than two" (really three or more) is that I've found, doing a lot of support programming over the years, that tasks come in three forms--the one-off, the one-off you screwed up and have to redo, and the repeater. (Or the one, two, and many times cases)
I know the traditional CS counting scheme is "0, 1, or many", and that's more or less true for counts on data instances, but I've found in practice for writing code segments it's more "0, 1, 2, not again!"
The monkey comment was there to make people realize that, if the job requires no brain at all (we're presuming the monkey isn't smarter than the person doing the task) then a program should be doing the task, and you'd be far more effective writing a program to do the task rather than just doing the task. (Time permitting, of course, and it often doesn't) | [reply] |
