(Though I wouldn't dream of arguing that the end result of the HR system is more fun.)
Later on I've started to notice that those who never develop their skills this far tend to boreout of the career earlier. I hypothesize that at about the ten year mark, programmers fall reasonably cleanly into one of three categories: 1. approaching the job the way I do 2. boredout of the career or 3. immune to boredom, the traditional old fogey who doesn't keep up and only knows COBOL (or whatever fills the niche for when the programmer started), and the ones who give us #1s a bad name. I plan on keeping my eye out for this in the future. (That is, when I say "I hypothesize" I mean it's a new hypothesis I mean to test, but do not have any immediate counterexamples.)
So yes, ostensibly everything can be automated, but many things are boring and repetitive yet resist automation, while for others, introducing automation is either too much work to be worth it in the first place, or just introduces more code you need to maintain.
But these kinds of jobs can have their upsides...
(Of course, when the manual solution proves error-prone or the "one-off" problem "unexpectedly" arises a second time, we all know who gets the last laugh...)
Fast forward to where I am today, writing HR applications on a much larger scale, and the funny thing is we're solving the same problems we 'solved' years ago, just in a different, more enterprisey (read: slow, buggy) way. Its both sad, and amusing to watch from a distance.
That said, even the most boring of application will give you a rush when you hit a breakthrough. I once got excited over finishing a brute force solution to a problem in college. Sure, it was inefficient, but I wrote it, and it worked.
2008? We've had a generation of movies, books, etc. in which this idea is one of the main themes at the very least. Office Space, anyone? Fight Club, even?
I was wondering about this the other day - does lazy have a real meaning? I thought through some options and came to the conclusion that it's a nondescription used to close off any further enquiry and also used as an insult.
It doesn't explain anything, it's a proper phlogiston answer.
Not doing something could be lack of motivation (that doesn't matter), lack of interest (I don't want to paraglide), other priorities (I would but can't right now), lack of skill (I want to but can't), fear of various things (if I start I will only draw attention to this, what will people think, what if I fail), but lazy? A nonsense word which I should stop using.