Again, mostly yes. Another way I look at a "lazy programmer" is in the way of how a developer works. If a "lazy" developer has to do the same thing 3 times, the

Again, mostly yes. Another way I look at a "lazy programmer" is in the way of how a developer works. If a "lazy" developer has to do the same thing 3 times, then they will figure out a way to automate it. A "lazy" developer also tries to find the best tools for every job, and figures out how to best leverage those tools for maximum productivity and least effort. Whether it be the right language for a task at hand, to using macros and powerful editors (to perform "surgery" on text [I quote Yegge here]) to learning keyboard shortcuts for their IDE of choice so to minimize hand movements etc. This also applies itself to not violating DRY, to thinking about higher level of abstractions so as to reuse code better, writing modular functions that are easily accessible and do not violate the Principle of Least Surprise. I know I am missing a lot here, but in conclusion, I agree with you about the article.