1. Desiring efficiency, so one can achieve more with less effort.
2. Not wanting to think very hard, and putting off difficult decisions.
This article argues that programmers aren't number 2. I'd agree. Others argue that programmers are number 1. I'd agree. There's no conflict here, just confusion!
For example: if you're in good shape you can run up a flight of stairs without any effort. But is getting in shape laziness? Not by any sane definition.
I'm sure you can think of a dozen other analogies, but they all illustrate the same thing: educating yourself, improving your tools, getting in shape are not laziness but the opposite.
And I think that's what original author meant. There is conflict between the definitions, and only the second definition indicates laziness.
Suddenly writing code cleanly becomes a very lazy thing to do, it reduces the amount of effort you have to invest in a program over the program's lifespan, unless its a throwaway and then ugly stuff makes sense.
Working out isn't a lazy thing, it is easier to climb a flight of stairs than to train 6 hours a week for a year and climb a flight of stairs. It increases the efforts you invest in things, it might be a goal to be healthy and energetic but then the lazy thing to do is to try to hack your training schedule and get the most benefit out of every drop of sweat.
The problem I see with many lazy programmers is they tend to hide how easy it is to fix problems over time. If might take them five minutes to do something, but they don't feel the need to share this with other people. But, in the end lazy programmers tend to get more done than average even if they don't spend much time actually working.
Could you point out where you got the definition for number 1?
"I program because I’m too lazy to do the same thing again and again!"
i.e. I want to abstract the concept of doing it into a computer program (or shell script, or cron job, or whatever). But the author understands "lazy" to mean something different, and more to the point, negative.
The point that I'm trying to make is that this argument is not about whether programmers are lazy, but it's about what people understand by the word "lazy".