In 2003 we first gave a talk at OSCON on PHP Best Practices. A lot has changed in six years—and a lot has stayed the same. Come with us on a tour of what we still get wrong, what we shouldn’t get wrong any longer, and why we all have to try harder than we once did.
We will cover:Of course, no best practice presentation would be complete without some examples of worst practices.
Luke Welling is from Melbourne, Australia, but currently lives near Washington, DC, where he ekes out a living as a security nerd at OmniTI. He sees lots of good PHP and bad PHP, and tries to write more good than bad. Over the last decade, he has applied PHP in many places where it was intended, and in many places where it was never meant to go. With his wife Laura, he wrote the bestselling book PHP and MySQL Web Development and often speaks about PHP at conferences and user groups. His hobbies include riding his horses and sticking Splayds in toasters, although he has not yet attempted to do both at once.
Laura Thomson is a Senior Software Engineer at Mozilla Corporation on the web team, after spending much of the previous decade as a consultant and trainer on various Open Source technologies.
Laura is the co-author of “PHP and MySQL Web Development” and “MySQL Tutorial”. She is a veteran speaker at Open Source conferences world wide.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at scordesse@oreilly.com
Download the OSCON Sponsor/Exhibitor Prospectus
Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the OSCON newsletter (login required)
View a complete list of OSCON contacts
Comments
Will the slides be available somewhere? They’d be much appreciated!
I’d have liked to get a little more in the weeds with some practical examples of what to do and what not to do (like showing code, etc). This was a little higher level than what I expected.
Great information. Personally, I could have let them talk at least twice as long.