PHP Application Development Part One - Conclusion (
Page 6 of 6 )
I hope this article has provided some insight into the basic fundamental considerations when planning and developing a PHP application. The need for organization in any application is self evident, especially to developers who have worked on someone else's (or even their own) ugly, unorganized code. This begins at the physical level, organizing files into meaningful directories and giving files meaningful names. It is continued at the logical level, where following conventions of style and linguistics lead to simple to read, clear code that makes its intent clear to the reader.
We have also discussed basic considerations for writing efficient PHP code – a topic that certainly goes well beyond the scope of this article, but which also has some simple considerations to keep in mind when building an application.
The next article in this series will cover more concrete application planning issues, such as data storage, logging, error handling, and configuration management and implementation. Throughout this series, we will build on the knowledge from previous articles and in the end, have a somewhat comprehensive guide to developing efficient, scalable, and maintanable PHP applications.
| | Discuss PHP Application Development Part One | | | | | | | I really like this article. It provides a lot of great information on good PHP... | | | | | | I will respectfully disagree with your comments =) PHP is a remarkably fast... | | | | | | Nice work! I always love to see articles relating to coding practices. Good luck on... | | | | | | Perhaps that is where my true disagreement is. I for one think:
"She has a... | | | | | | I will be mentioning templates later in the series and discussing why you should... | | | | | | Extreme example but compare the following two - find $chartype in each:
"Not only... | | | | | | All right, you've convinced me. Placing the variables outside of the string is... | | | | | | 0verall, this was a great article for covering basic PHP coding conventions. The... | | | | | | Thanks for the reply. I agree that using underscores is an acceptable convention,... | | | | | | In your article you stated;
------
<?php
$obj = &new MyObject();
... | | | | | | Somehow I did forget to mention that was fixed in PHP 5 - could've sworn I had.... | | | | | | Right. Good article.
I've noted a small mistake though:
<quote>
for ($i = 0;... | | | | | | It was my understanding that unless an object contained lots of data, such as a huge... | | | | | | ...I just wish I'd read it a year ago. It's comforting other people have to refer... | | | | | | On a similar note, I used to think while() loops were more efficient than foreach()... | | | | | | I did tests on this about a year ago and got some pretty dramatic results. I'm sure... | | | | | | Thanks for pointing that out, I'll make sure it's fixed. I promise I know the right... | | | | | | I think you meant "comma", not "colon", when you stated:
the correct spelling... | | | | | |
$myNumber = 2;
$myNumberSquared = Math::square($myNumber);
[b] print... | | | | | | Right!
Thank god I don't right articles... | | | | | | Yes, I like the underscore better for file names, because when you copy files... | | | | | | Just my two cents:
I've read somewhere that this:
echo 'Welcome back ',... | | | | | | I knew what he meant, the correction has already been made. Thanks =) | | | | | | I agree with satane and the previous poster; _ is my prefered method. I come from a... | | | | | | Your example, "did i name it myDb or myDB", implies a lack of agreed upon naming... | | | | | | What methods do you use to benchmark your PHP applications? Thanks.
Ben | | | | | | Not true. Passing echo parameters is slower than concatenation. I've done timing... | | | | | | You could do this in at least a few ways...
Use a load generator to check the... | | | | | | [quote]placing variables outside of strings increases readability[/quote]
I think... | | | | | | >>> Post your comment now! | | | | | |
|
 |
