Paul M. Jones is an internationally recognized PHP expert, working in that language since 1999, and programming in general since 1983. He has held roles from junior developer to VP of Engineering in all kinds of organizations (corporate, military, non-profit, educational, medical, and others). He is a regular speaker at technical conferences worldwide.

As the author of Modernizing Legacy Applications in PHP and Solving the N+1 Problem in PHP, Paul takes a special interest in high-quality, high-maintainability coding practices. His leadership on the Aura for PHP project reflects this interest, along with his white paper on the Action-Domain-Responder pattern.

Among his other open-source work, Paul was the architect of the Solar Framework and the creator of the Savant template system. He has authored a series of authoritative benchmarks on dynamic framework performance. He was a founding contributor to the Zend Framework (the DB, DB_Table, and View components).

Paul was a founding member of the PHP Framework Interoperability Group, and was the driving force behind the PSR-1 Coding Standard, PSR-2 Style Guide, and PSR-4 Autoloader recommendations. He was one of the first elected members of the PEAR Project. He was also a member of the Zend PHP 5.3 Certification education advisory board, and wrote some of the questions on that test.

In a previous career, Paul was an operations intelligence specialist for the US Air Force, and enjoys putting .308 holes in targets at 400 yards.

6 thoughts on “About

    • Hi Michael — glad you liked the talk, in spite of the awful sound quality.

      > How could a newbie become such a PHP guru like you in a short time?

      I’m flattered. If I am a guru, it took a long time of building up experience and doing lots of things wrong, and then remembering all the mistakes and things that didn’t work. Knowledge can be gained from a book, but wisdom can only be gained through life.

      > What and how should he practice to become such a craftman?

      I recall hearing that, if you want to become a good writer, you should (1) read good writers, but especially (2) become a good *editor* of other peoples’ writing. I think the same thing applies to programming: reviewing lots of code from other people, and edit lots of code from other people.

      Hope that helps.

Leave a Reply

Your email address will not be published. Required fields are marked *