Hi Troy,

I think there have been very good responses here all around. Fortunately I've been lucky in many respects to have been in the middle of things, and many times the lead role, when I was with an old employer. To their credit, they recognized the importance of the developer having an understanding, not only of the overall goal of what's to be achieved, but also how it will be received by the end-users, clients, etc.

What has your experience been? Have you been able to get involved in the areas that you feel would be advantageous to the company/project?


- Brian


>
>I guess what I am fishing for here, is that I see extreme advantages to a developer being part of even more than specs and coding. Things like how a product is going to be marketed or how it is going to be billed to clients, or even what kind of people will be using it can all have an impact on the end product. Developers, most likely being the ones in tune with what is going on in the computer industry, can be very valuable in exchanging ideas with these respected areas at the drawing table because the developer can give immediate feedback on what they have seen, what cool things are out there and what kinds of things are possible.
>
>In addition, on the end side of a project the developer can work with tech support so they know what kind of potential problems may arise and how to fix them.
>
>Troy