>Hello Troy,
>
>There have always been programmers and developers. Programmers IMO are code jockeys which are tightly controlled and limited in scope, this has never interested me. Developers are designers, planners, analysts, programmers, testers, trainers, etc. This is where the real action (and money) is. This requires alot more knowlege, not only of programming, but of business, human nature, people skills, and organization. I wouldn't want to be involved in projects where I wasn't involved in the big picture.
>
>Bob
>
>>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

Bob;

I worked for a company that did addons for a third party software product. Every “deal” was done without a software developer and the “solution” (third party product) plus and all custom software was defined – but not well. To get the deal the salesman would tack on 10 hours for system set up (we provided all computers and hardware), customer training and all custom software.

I had just been hired and the other programmer quit. I found out why shortly. He was working on a typical project, and it was given to me. I called the client and found out what in fact was required. In fact I drove to the client site and had a meeting with several departments. This was for a well known University in California. After determining the needs of the client I came up with an estimate 280 hours. This did not bother the owner of the company but it had me concerned. We had just hired a new general manager and I went to him as the owner had promised the world to the client and wanted me do nothing. The general manager and I set up a second meeting with the client on a Friday. After the meeting the GM said “We are in deep trouble”! Monday morning the GM quit – he had been there only about 2 weeks and had seen enough. The client sued and the owner did not seem to be upset. In fact being sued was a way of life for him. I quit not long after this as I had had enough. The owner went on to sell the company for $7 million. Such is life.

I have the impression that I can never be a salesman.

By the way - titles mean little - it is the job requirements that are important. I have had a number of titles at different companies where I have been employed. Consultant, Visual FoxPro Programmer, Programmer, Software Developer, and now Staff Specialist. What is a Staff Specialist? I get to do it all when it comes to writing a software application and I do mean everything!

Tom