Hi everyones,
I coding PHP since 2002 and this is the first time I have to take this
decision.
My group and I have to build a VERY, VERY BIG website for a callcenter
users. Understand I have to create (or use ;)) several code for access,
transactions and management.
The customer had buy
I don't know about whats best for the compiler (rather interpreter), but if
it is a really big site with a lot of access, transaction and management
functionality I recommend you start breaking the code into classes and
separating each class into a file and documenting... A LOT! It will be
clearer
Definitely sounds as if you should be employing the object-orientated
methodology, If the project is as big as you say it is then really you
should be looking to use some UML planning tool so that you can keep all
you code organised.
It is ok on smaller projects to bash out some rough plans
Martin Leduc wrote:
Hi everyones,
I coding PHP since 2002 and this is the first time I have to take this
decision.
My group and I have to build a VERY, VERY BIG website for a callcenter
users. Understand I have to create (or use ;)) several code for access,
transactions and management.
4 matches
Mail list logo