Re: Strategy when working with designer(s)?
| From: | Larry Garfield | Date: | Tue, 24 Jul 2007 00:17:55 +0000 |
| Subject: | Re: Strategy when working with designer(s)? | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-259401@lists.php.net to get a copy of this message | ||
On Monday 23 July 2007, Simon wrote:
> I recommend:
> 1) Designer does his whole job and shows the design when finished and
> approved 2) Integrator works on making the pages and html without func.
> 3) Programmer makes the whole thing work.
> This gives the best feeling to all people involved.
>
> All IMO!
>
> Simon
That's our usual routine, too, except that the designer is outsourced and then
we have our "Developer" (HTML/CSS guru) and "Programmer" (PHP/Javascript
guru) both function as integrators of sorts.
However, always make sure that the programmer is there and involved from day
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
programmer involved in the project, even if no coding happens until far
later.
--
Larry Garfield AIM: LOLG42
larry@garfieldtech.com 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