On Tuesday 24 July 2007, Simon wrote: > > 0. The designers we work with frequently need to be told "that 3 second > > feature you just suggested just added 300 hours to the project and > > destroyed 508 compliance", usually multiple times. That *must* happen > > before the client sees it, or you're screwed. It's never too early to > > get the > > Yea! > I have always seen the programmer as the Leader* of the production of > the project. He is the one to give the final word on what is Possible > or not, and that is precisely what cause most problems (also known as > scope of the project). > > *I am the programmer, maybe my perception of project hierachy is > biased by my ego? ;) > > Simon That may well be a factor, but it's still true. :-) The programmer doesn't have to be the PM. Very often programmers make lousy PMs. But the PM needs to have the programmer and the developer (HTML/CSS person) with them from day 0, and give both a voice. Short changing one and favoring the other will only make both miserable. (Because when the programmer comes back with "the form you mocked up is logically impossible, here's how I was able to do it, you get to redesign it now", the developer, designer, and PM are all made miserable, too.) Not that I am speaking from personal experience of course, no, not at all... -- Larry Garfield AIM: LOLG42 larry@xxxxxxxxxxxxxxxx ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
