Evolution of a Programmer

In a recent discussion about the Intentional language workbench on the Software Craftsmanship mailing list Dave Hoover made the following comment:

If programmers from 30 years ago looked at my typical day today, I bet they would think I was more of an analyst than a programmer. The high level code that I get to work with typically keeps me very close to the domain language of my customer... the problems I'm generally solving aren't related to computer science and optimizing milliseconds, they're translating my customer's desires into executable software.

I thought this was interesting and I agree with Dave. To some extent I wish this was even more true than it already is. Writing software and solving problems 'close to the metal' can be interesting and rewarding, but being able to bring my ideas and my customer's ideas to life quickly and elegantly is really what it is all about for me.