any problem you had face and wish to tell me... ?
what problem you face when developing large scale PHP web application?
crappy design
performance
stuff made fast so u can throw it after a couple days and it becomes a major and unavoidable component of your IT
performance
lack of cigars
lack of cognac
version conflict
performance
etc.
Poor planning. When developing ANY large application you can't do it without some good planning. Unless you can visualize the entire thing in your mind when you're creating it, it's going to get messy. What we do where I work is usually code seperate modules for each section of the application, and link them all together afterwards, just to keep it neat. But seriously, plan and document everything, because when you come back to it later, you're not going to know what you did, and why.
Losing sight of the end.
I'm not only a programmer, but I design everything as well.
I'm currently working on a web based administration system and have been doing so for the past year.
Tired...
Planning for future expansions or additions, reading the minds of clients, and trying to make them understand the limits of the physical programming world.
-Elizabeth
A MISSING SEMI-COLON OR BRACKET!! arghs
21 days later
Poor documentation...
I once wrote a large scale web app in PERL with no docs and after about 6-8 months of it running fine our webhost reconfigured our server without telling us...
In any event I had to go through literally tens of thousands of lines of codes in hundreds of different files trying to find all of the file paths to all of the necessary data files and change them...
And no, I never did get it working again...I rewrote the whole thing in PHP...with better docs...
Chris
my boss looking over my shoulder and constantly asking when "the thing" will be ready
this is not motivating...
Not knowing what your getting into
This is, I guess, in particular when you're a n00b like me 
... I started on several apps, thinking it's going to be easy peasy...
NOT!
I useally wind up giving up becoz it's all way over my head, and the code isn't structurized (thinking a lil thing like this doesn't need structure)
talk about your large scale project architecture?
define large scale project architecture
large scale... in my H context
- users who use it > 2000 persons per day.
- involve many DB query which i got to paged them into page or file.
- a separation of code and presentation layers.
- security issues.
but i found it hard to do total separation of code and presentation layers.
i want my scripts to be manageble which in my context is
less file. maybe 4 => 5 files (core files) to rock application.
i found it hard to manage when files grow to 15+
i think in developing large scale web application... issues i / we face :
1. building the form (many forms) again and again for the user to interact with users. <= which in my opinion, these should autobuild based on our SQL create table when installing.
thinking TOO much of the security problem, where i am not so sure whether i can hack my apps or not but 60% in my mind tells me i can hack it if i start to think how to hack it.
don't want to do things again and again, wish there could be same sort of AI that deal with the again and again task. But the moment start using the AI, customization power will be low or the AI is dumb?
have some bias toward template method to deal code and presentation issue. but can't think any good idea to deal it.
after all, web application is a database interface.
IMHO, web application should stand on its own when
- i already suppy it process code.
which i mean, the framework should do all the dirty jobs.
some peeps use one file to display all things.
some peeps use many files to display all things.
some use combination
or any other new method?
Hehe you guys r cool.. I visualise my entire site, and revise it, clean it up when im bored
http://socceraddicts.com/phptsunami3005/
Messy buisness I want to know a good way of having all the site coded serperate and link them 2 gether like dat dude was sayin?
I use include to load the pages up keeping 2 one design.. but im using functions at the top of site and calling them on if statements.. depending on form input.
Any ideas? I like to have a module type of thing goin on, where a friend can code a module and I can link it up without hard coding it.
Starting it off. But never finishing it because you cant see the light at the end. Im making a Forum got the Admin 1/4 done. And damn its taking its time.
Oh + doing a large scale project while havin lots of other work which needs attention first. making it harder to get back into
Prioritising between one project and the next. Currently, I have two projects on the go for work. One is in ASP (which I am still learning) and one is PHP (yey!).
The ASP one is kinda finished but I'm adding more stuff to it and the PHP one has to be done by the beginning of September.
And I'm sure I'll have loads more projects shoved my way.
My main problem is staying focussed. Also, working out the dependencies between components, because I usually end up going off down branches as I write piece after piece of dependent components, thus losing focus on the main part.
Oh, and then there's the looking back thing, where you see what you wrote last year and go "Urrgh".
A thousand path journey always starts with a small step.
Make realistic goals for each version. Incrementally adding features. NO NO YOU CAN'T START CODING EVERYTHING.
Start from precise, fog-free requirements.
Use them and make them evolve as your project goes on if necessary.
Start witht the hardest piece so you don't have a major surprise 3 days before production day.
Test, test, test and test again.
Document. Document the documentation.
Structure everything more than I did my post.
looks like my .php framework still have a long way to go... 