>Al,
>
>Just some general thoughts. None of the statements herein are directed at anyone in particular. They're just generalizations based on my observations.
>
>I've always believed that programming is about solving problems, not languages or methodologies. I think part of the reason that things haven't gotten any easier is that we're being asked solve increasingly more sophisticated problems as the technology has advanced.
>
>However, in solving these problems, there are numerous pitfalls along the way. Any one of these can make the task considerably more difficult than it should.
>
>Failure to either understand or to not get accurate requirements of what needs to be done is a potentially disasterous pitfall. It can lead to solving the wrong problem or implementation that doesn't completely address the one at hand.
>
>Using the wrong tool can create problems. There are times when I need to use C/C++ and times when I need VFP.
>
>Not employing sound design principles can make things terribly difficult. Using bad methodology can likewise make things harder.
>
>Doing or failing to do proper testing to assure the accurancy of the results.
>
>There may be more. These are just the ones that come to mind off the top of my head.

I think most would agree with all of this. About your first point, "solving problems", how much of our time these days is spent addressing business problems, versus "solving problems" related to/caused by/inherent to the complexity of the technology involved?