I try to go with doing whatever gives the most business value first. This
means whichever piece of functionality is most important in getting the
application working in the shortest amount of time. You can then release
this part to the testers immediately and get feedback early.
However, on my
I'm building my first site in CakePHP. It will involve a few different
sections that users will need to log in to post on, and I'm uncertain
about in which order I should be developing the site. This is the
first large-scale web app I've ever built; all prior PHP experience
has been for brief
On Jan 9, 2008 3:28 PM, 703designs [EMAIL PROTECTED] wrote:
I'm building my first site in CakePHP. It will involve a few different
sections that users will need to log in to post on, and I'm uncertain
about in which order I should be developing the site. This is the
first large-scale web app
I used some of Chris's links, so I can recommend them. :)
Personally, I'm building out user security, authentication, access
control, session management, logging and testing first. They're all
pretty important elements, and I want to make sure they're right (or
at least working) before I move
I agree with Chris, it really doesn't matter which you do first, using
functions like beforeRender and beforeFilter you can easily add your
authentication in one place after your site is complete. But then
again there's not reason not to do it first either. Just whatever
you're preference is I
