>It seems from my observations that the trend not so many years ago was that the developer’s role had evolved to be, simply stated, a programmer. He/she received requirements and wrote code based on those requirements. There was a so-called “box” around the developer’s responsibilities. Now it looks to me that the trend has changed (in my opinion, for the better) where now more often the developer will work along with an analyst and learn the business on different levels. The developer may sit in on business meetings, perhaps even meet with clients.
>
>I’d like to hear some opinions from fellow developers on this subject.
>
>Thanks,
>
>Troy

Yes, sad but true. It's rare that I have the luxury of getting a spec and I'm increasingly expected to understand complex business practices of which I neither care about nor wish to focus on. I prefer to focus on the solution at hand and how best to build it. You don't see construction contractors getting asked to develop blueprints, do you?

Oh well, suppose we'd better get used to it.

-JT