![\"PHP](\"http:\/\/www.bin-co.com\/blog\/wp-content\/uploads\/2008\/09\/php-logo-1-1.png\" "\\"PHP"){kind=logo}
<\/p>\n<\/p>\n
Are you a PHP developer? Go read the article ‘10 Principles of the PHP Masters<\/a>‘. Do you want to learn PHP? Go read it. <\/p>\n With PHP’s widespread adoption,it’s almost too easy to find a script or snippet to do exactly what you need. Unfortunately, there’s no filter as to what is a “good practice” and what’s, well… not so good when writing a PHP script. We need trustworthy sources, who have proven they have a solid grasp on the best practices of PHP.<\/p><\/blockquote>\n Rasmus Lerdorf<\/p>\n PHP was designed for Web Development<\/a> – and its very good at it. Just because you can use it to create desktop apps don’t mean that you have to.<\/p>\n Matt Mullenweg<\/p>\n This advice comes from a rather controversial database design choice he made when creating WordPress MU<\/a>. It created separate tables for each blog rather than the usual method.<\/p>\n Dave Child<\/p>\n Validate everything<\/a> that comes from the user. Yeah, I know its boring – but it must be done.<\/p>\n Ben Balbo<\/p>\n Caching is very important<\/a> if you have a busy site.<\/p>\n Chad Kieffer<\/p>\n I find it a bit hard to support this. Yeah IDEs speed up development<\/a> – a small bit. About Snippets – use them if you trust the source.<\/p>\n But if you really want to speed up development, <\/p>\n Joey Sochacki<\/p>\n This is actually new to me – but I am going to try this out.<\/p>\n Filtering data<\/a>. We all have to do it. Most, if not all of us, despise doing it. However, unbeknown to most are PHP’s filter_* functions, that allow us to do all sorts of filtering and validation. Using PHP’s filter_* functions, we can validate and sanitize data types, URLs, e-mail addresses, IP addresses, strip bad characters, and more, all with relative ease.<\/p><\/blockquote>\n Josh Sharp<\/p>\n This is one thing that really speed up development. Also, the programmers that have to maintain your programs will thank you for it.<\/p>\n Rasmus Lerdorf<\/p>\n The basic argument is that Frameworks slow things down<\/a>. Keep that in mind when your choosing a framework.<\/p>\n Jack D. Herrington<\/p>\n This refers to the tasks that can processed in the background – Herrington recommends using batch processing and cron<\/a> here. As most of you are aware, PHP don’t have threads – and it don’t matter to me. You don’t use threads when serving a web page. But in cases like these, threads come in handy.<\/p>\n My advice? Use Python or some other language that has threads to do do the job for you – you don’t have to do everything in PHP.<\/p>\n David Cummings<\/p>\n This is very important when developing the app – error reporting lets you find future bugs<\/a>. Make sure they are on.<\/p>\n And just as important is the fact that you should turn them off in the production system – you don’t want your users seeing your error messages.<\/p>\nUse PHP Only When You Need it<\/h2>\n
Use Many Tables With PHP and MYSQL for Scalability<\/h2>\n
Never, ever trust your users<\/h2>\n
Invest in PHP Caching<\/h2>\n
Speed up PHP Development with an IDE, Templates and Snippets<\/h2>\n
\n
Make Better Use of PHP’s Filter Functions<\/h2>\n
Use a PHP Framework<\/h2>\n
Don’t use a PHP Framework<\/h2>\n
Use Batch Processing<\/h2>\n
Turn on Error Reporting Immediately<\/h2>\n
Related Links<\/h2>\n