I've long said that all programmers are lazy. There are
two kinds of lazy, though. Good lazy is when a
programmer has to do something twice, she stops to automate the
process, so she won't be bothered by this rote task again. Bad
lazy is when a programmer uses "clipboard inheritance", mindlessly copy
and pasting code, and not stepping back long enough to find a better
solution, much less the "best" solution.
This was brought to mind again by a post by Phillip Lensen (via
Foxpro.catalyst):
Why Good Programmers Are Lazy and Dumb
I hadn't considered the dumb part, but I do look for a drive to
constantly investigate and learn when evaluating a job candidate.
Phillip makes some interesting points.
++Alan