I use the term intelligent laziness, that is the constant desire to minimize the effort you will need to invest long-term in your life to achieve your goals.
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.
I think the confusion comes from applying real world constraints to code. Most people would be in shape if you only needed to get in shape once and you maintained that body with zero effort over time. Lazy programmers recognize you only have to build the code once to benefit every time you use it. So building tools can be useful but only if they are going to save you effort over time.
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.
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.