Conclusion - PHPSettling for the "quick and dirty" solution often costs far more time than it saves. This is as true of PHP coding practices as anything else. In this first article in the series, you will learn practices that will save you time and headaches in the long run, and help you write better PHP code.
print this article SEARCH DEV SHED |
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.
blog comments powered by Disqus |
/ 106 
PHP Closures as View Helpers: Lazy-Loading File Data
