John posted another follow up on the laziness discussion.
I think Eli, John, and others who have weighed in have really hit it on the head. It's not just about being lazy - anyone can just sit on their ass, after all - it's about long-term laziness. The idea being that a little extra effort now can save me a lot of time and effort and headaches in the long run.
A good, albeit simple, example of this is building and maintaining a simple website. I've done a number of sites for non-profit organizations I'm involved with, which inevitably need to have some new content added. Those responsible for the content are by no means technical - asking them to edit HTML is asking a lot.
Typically, they might just e-mail me content, which I would cut-and-paste. This model isn't scalable, of course. I can take myself out of the critical path for content updates, however, by building some sort of content management tool. I've enabled those who are responsible for the content to be responsible for the content, such that they can do what they need to do without depending on anyone else.
More importantly, I'm no longer a bottleneck. I may have spent a bit more time upfront building this than I would have if just putting up a static HTML page - but in the long run, it makes my life easier. This is what I consider lazy. I work a little harder to make sure I don't have to work so hard.
The same is true for a well-factored component or framework. When something is extensible, consumers of the framework can add or change functionality themselves. I save myself from having to do these updates for an unbounded period of time, all because I took the time and put a little more effort in upfront.
We often have this discussion as far as upfront implementation costs versus ongoing maintenance costs. When you work it out, depending on lifespan of course, doing something right the first time, or having the discipline (or laziness) to refactor, is inevitably going to save you time and effort in the long run.
In my mind, lazy programming is not about taking shortcuts. It's really about lowering your total effort over time (especially when the effort is mundane).