Hmm, I'd have to disagree, if there is going to be a project manager, then that is the person who has to make everyone happy. Inevitably in my experience if I try to talk to a client too much about their site, I start thinking about the code as we talk, which leads to me influencing directly what the finished product looks like, because they are bouncing ideas off of me, and I may not be thinking about what benefits there are to the client, but how I am going to have to change the database... I don't think this is a good idea, the programmer should be transparent to the whole process. Of course the programmer should stand up when something doesn't make sense, but otherwise saying, something can't be done is almost always wrong. If you someone can dream it up, the programmer should be able to implement it, in the most logical way. If however, the only requirement is "A peice of software that designs efficient widgets", then the programmer(s) should obviously be involved in the design process.
Besides, I'm always happy with my code...until a year later when I look back :) ----- Original Message ----- From: "Nick McClure" <[EMAIL PROTECTED]> To: "CF-Community" <[EMAIL PROTECTED]> Sent: Wednesday, March 27, 2002 3:37 PM Subject: Re: Conversations... > I don't disagree with this, As a programmer you responsibility is to make > everybody happy. the company, the client, the public(maybe), and yourself. > <snipage> ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
