Lazy, because only lazy programmers will want to write the kind of tools that might replace them in the end. Lazy, because only a lazy programmer will avoid writing monotonous, repetitive code—thus avoiding redundancy, the enemy of software maintenance and flexible refactoring. Mostly, the tools and processes that come out of this endeavor fired by laziness will speed up the production.
Doing your best to get around any extra work certainly sounds like the definition of laziness. But Lenssen asserts that in the process of eliminating those unnecessary steps, the “lazy” programmer also is getting rid of future drudgery. If this programmer has to do something more than once, he will consider automating it, thus speeding up and improving the process.
Being lazy also will drive a programmer to determine which software tools make work easier and to ensure that work can be maintained and refactored easily. A lazy programmer will find tools that help him stay lazy instead of creating a tool himself, preferring to take advantage of the efforts of the open source community. If there is an existing solution that has already been tested and proven, this programmer will find it—and once again, his laziness has actually streamlined productivity.