>I think it depends on the situation. We have more junior level programmers
> who do more sit down and write code. The higher level guys do more design
> and spec work, but also some coding.

I agree. I think there should, and most of the time MUST, be a place for both types in a successful organization.

Some people want to be programmers. They love to sit in front of a computer and not be interrupted by outside influences. There is nothing wrong with that.

Still others may be perfectly capable of coding, but are not interested in it as their sole job. There is nothing wrong with that either.

I think a successful organization will take advantage of these two "types" for a well-rounded organization. I'm not sure I agree, however, (forgive me if that's not what you're saying) that one should necessarily be a higher position then the other.

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