On Mon, July 23, 2007 3:00 pm, Steve Finkelstein wrote:
> This is more of a conceptual based inquiry. I'm currently working on
> some projects which require me to build system 'X' prior to any
> (X)HTML/CSS/graphics are available to me. A lot of the time, I just
> garble up default tables/forms/ima
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'
The 'Leader' should be an IT Architect who understands both:
In a dream world we can pay such a character, what I've seen so far is
we "invent" one out of the guy that knows most: the programmer.
(Instant promotion, same salary)
From my experience, the project manager would ask the programmer
On 24/07/07, Simon <[EMAIL PROTECTED]> wrote:
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).
The 'Leader' sh
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
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.
Steve Finkelstein wrote:
Hi all,
This is more of a conceptual based inquiry. I'm currently working on
some projects which require me to build system 'X' prior to any
(X)HTML/CSS/graphics are available to me. A lot of the time, I just
garble up default tables/forms/images to replace what the desi
s God. Don't let sin keep ruling your
lives.You are ruled by God's Kindness and not by the law.
Romans 6:12-14
-Original Message-
From: Simon [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:22 PM
To: Steve Finkelstein
Cc: PHP General List
Subject: Re: [PHP] Strategy whe
I have experience with designers.
My suggestion.
Don't code anything client-side until they are finished, you will most
likely have to change everything.
You can do your functionality (login mechanism, password change,
listing, query with db, etc...) and be ready for when they give you
their mon
On 7/23/07, Steve Finkelstein <[EMAIL PROTECTED]> wrote:
Hi all,
This is more of a conceptual based inquiry. I'm currently working on
some projects which require me to build system 'X' prior to any
(X)HTML/CSS/graphics are available to me. A lot of the time, I just
garble up default tables/forms
Steve Finkelstein wrote:
I was curious how do you folks who strictly do development and not
designing, strategically work with a designer in this fashion? Do you
have a skeleton you follow or preload some existing templates and then
code around that? If there's even a book which focuses on such
Hi all,
This is more of a conceptual based inquiry. I'm currently working on
some projects which require me to build system 'X' prior to any
(X)HTML/CSS/graphics are available to me. A lot of the time, I just
garble up default tables/forms/images to replace what the designer will
be ultimatel
12 matches
Mail list logo
