Skip to content


Whirlwhind review of php|tek 09

It's been a simultaneously long and fast week for me. I flew into Chicago last Sunday, ready for the PHP core developers meeting that we had planned for the Monday and Tuesday. My journey went like a charm; perfect timing had me parked at the airport, immediately on the shuttle bus to the terminal, straight through security and to my gate just in time to start boarding. The only minor hiccough was in finding the shuttle from Chicago to the hotel; it was extremely poorly sign-posted.

Anyway, I got to the hotel and ran into the British contingent of the conference, and we eventually found our way to a Mexican restaurant not far from the hotel, and then to the bar across several lanes of traffic from the hotel, where a fair quantity of alcohol was consumed by all.

The next day we headed downtown to the Microsoft offices for day 1 of the core developer meeting, where a number of internals issues around PHP 6 were discussed. This was a very productive session, and we earned the drinks that followed at the Map Room, although I opted out of the bulk of those and headed back to the hotel (yes, I'm getting old)

Tuesday was day 2 of the core developer meeting, and thankfully was held in the conference hotel; the journey downtown took the better part of an hour and I was glad to skip it. The agenda for this day was to look primarily at what we could clean up in the code for PHP 6 and whether we might need to introduce a PHP 5.4 to aid in that transition.

We also touched on PDO 2; the short of it is that it might be about time to see if the vendors are willing to play with us again, and where the original plan was to have all the major vendors on board, we may well be looking at cutting out the less flexible vendors from the baseline PHP distribution. I'll do what I can to help facilitate a PDO 2, but don't anticipate having much free time in the coming months.

After a low-key dinner in the hotel sports bar (thanks Chris!) I retired to my room to catch up on a bit of work and put some finishing touches on my presentation deck. I returned to the bar a bit later to see who was around, and was surprised that most folks had turned in early; another sign that we're collectively getting older.

Wednesday was the start of the conference proper, and Andrei's keynote reminded us of the humble beginnings of the world-wide-web and took us through the various incarnations of PHP-past as a lead-in to PHP 6. As is usual with Andrei's sessions, I was left feeling a little jealous of the beautiful photography and humor he manages to find to complement what would otherwise be a somewhat dry technical presentation.

Later in the afternoon, it was my turn to present my new talk, which is partly best practices (really what I consider to be the baseline practices for any serious commercial development shop) and partly a re-hash of an internal presentation I gave to my team at Message Systems when I became Director of Engineering. I was pleased (perhaps even a little surprised) to find that I had a very full room for the talk, and happy that I seemed to keep everyone well engaged through to the end. I've had some good feedback and welcome constructive criticism so that I can improve it for the next time I use it; you may comment (anonymously if you wish) via the page for that session.

I sat in on Maggie Nelson's talk on ORMs, which was an interesting comparison of PHP ORMs. Personally, I think that ORM is one of those niceties that is, unfortunately, a bit too far divorced from the ugly reality of making things work well under load in the real world. There are some articles out there on the impedance mismatch that leads to most of the problems, and some interesting work from my colleagues at OmniTI in the form of a Relucant ORM for Perl that avoids the major pitfalls.

After dinner, an open bar and a series of lightning talks put pretty much everyone in high spirits (that and consuming spirits...) that carried over into the wee hours of the following morning.

The next morning was largely playing catchup for me; both with some work and with various folks around the conference; new acquaintances and old friends. I was interviewed by Keith Casey about what went on in the PHP Developers meeting, and I think this is my first appearance on YouTube (and don't I look a little caffeine deprived?)

I caught Lorna Mitchell's session on Linux-Fu for PHP Developers which made me think that the growing number of self-taught Linux users, and the common develop-PHP-apps-on-windows-deploy-on-unix scenario does warrant some attention on what might be considered fairly basic unix know-how from PHP conference organizers. It was a good session and well presented.

After lunch, I had the (somewhat dubious!) pleasure of experiencing Eli White's gratuitous use of Knight Rider clips to highlight that you can make just about any programmer better if you give him the right tools.

The final session I attended was Chris Cornutt's session comparing a number of the popular PHP frameworks, which I found to be quite a useful comparison of their strengths. There was some drama towards the end when rival framework proponents in the audience had a somewhat heated discussion between themselves.

And shortly after that, I set out on my journey home, which was sadly rather more traumatic that the outbound journey, starting with a hot and sticky Chicago airport, a slightly delayed flight, which also had faulty air conditioning and the coup-de-grace in the form of a dead battery and faulty alternator in my car (actually Juliette's car; I let her use my car while I was away).

After a couple of assists from the airport transportation folks and local police(!), I got the car running and re-enacted my own version of the movie Speed, except that I had to keep the engine revving above 2000rpm or my electrics would fade out and the engine stall. This had me riding both the accelerator and brake pedals at the lights around the airport before I could get out onto the highway; something I think would have been easier to deal with if the car had been a manual transmission.

As ever, it was great to catch up with the usual suspects, and also to finally meet some of the younger blood in the PHP community face to face. I don't know if it's just that the majority of my fellow speakers are becoming increasingly senior in their respective jobs, or if there has been something of a shift in the industry, or if it's just me being focused into more of a managerial role in recent times (or some combination of these), but it seemed to me that there was more of a focus or awareness on practical engineering at this conference than I recall in past conferences.

I think this is a good thing because the typical PHP developer does not usually have a rigorous background in computer science or other "equivalent" scientific or engineering discipline. A few of us had a lunchtime discussion about how even the schools that are teaching computer programming tend to be skimping on applied software skills (the meat and potatoes of getting the work done, rather than just the raw programming theory), and how programming as a profession could benefit from having something akin to an apprenticeship scheme. It will be interesting to see where this train of thought leads.

Anyway, in summary: php|tek 2009, two thumbs up.

Thanks to Microsoft for hosting part of the developers meeting, Marco, Elizabeth and Arbi for the rest, Keith for the unconference, everyone whose photos I've linked in from flickr, and everyone else that attended for making the event what it was. I'm looking forward to the next time that I can attend :-)

Seven Things

I'm usually no big fan of chain letters (it's the "or-else" part that I object to), but this current 7-things-tag going around is pretty benign, and I think it's a great way to get some insight into the people you're reading. Thanks to Elizabeth Smith for tagging me.

Anyway, here's some facts about me that you may not know:

  1. I have 6 siblings: 1.5 brothers and 2 sisters.
  2. I used to live in Spain and crossed the border to Gibraltar twice daily getting to and from school.
  3. I taught myself 6502 machine code on the C64 when I was 10. 'C' had to wait until I finally got my own Amiga at the age of 17; by that time it was already obsolete, but I'd dreamed of it for so long. The biggest barrier for learning 'C' for me was the sheer quantity of bad Intuition code examples floating around on Fish Disks and Aminet.
  4. I studied Electronic Systems Engineering at The University of York, where I discovered my first Unix system (IRIX) and had to retake my first year exam as a result of spending too much time in the "Spod Pit" (a room filled with Indigo workstations). In retrospect, that "inappropriate" use of time was instrumental in shaping my career.
  5. I once rolled into a 9 a.m. computer lab assessment with my partner wearing tuxedos after partying all night at a graduation ball. The lab supervisor said "let's assess you first, as you look like you've got places to go". (We aced that assessment; preparation was key).
  6. I've moved home on average about once every 2.5 years of my life, making my time in the USA one of the longer periods in one spot.
  7. I've been told that I have a distinctive look, which is probably largely due to my long hair. In the late 80's, early 90's, I used to have a flat top. Then I discovered Guns'n'Roses and Metallica and haven't worn my hair short since.

As for chaining, in no particularly significant order:

and the rules:

  • Link your original tagger(s), and list these rules on your blog.
  • Share seven facts about yourself in the post - some random, some weird.
  • Tag seven people at the end of your post by leaving their names and the links to their blogs.
  • Let them know they've been tagged by leaving a comment on their blogs and/or Twitter.

Wanted: Senior Backend Web Engineer

I'm looking for a senior-level engineer to help extend the web-based dashboards for our messaging infrastructure platform.

This position reports directly to me.

While we don't face the traditional scale-to-the-world types of problems in our web UI, we do face some difficult UI and data scalability challenges.

If you're interested, please contact me via

Job Description

You will enjoy in-depth exposure to all aspects of building scalable applications as part of a small, internationally-renowned team that helps our customers -- service providers and hot startups alike -- achieve their cutting-edge messaging goals.

Message Systems is a global leader in messaging, with a global customer base including tier-1 telecommunications carriers, email service providers and online enterprises. Our technologies help transit billions of messages per day for customers worldwide, while offering unmatched flexibility and architectural clarity. The company combines the best aspects of Open Source, startup, and established company in our business goals and corporate culture.

Message Systems believes in a fun but focused development environment. We have flexible hours, outstanding benefits, and a world-class team. Our engineering group works in an open plan and uses the Scrum development methodology with a focus on collaboration, automation, and testing.


This position involves leading the backend design and architecture for our dashboards. Qualified candidates should have current expertise developing robust web applications that can scale to large datasets.

Candidates should have strong PHP skills, at least 5 years of professional programming experience, and experience and good understanding of:

  • UNIX (Linux, Solaris or FreeBSD) based PHP development
  • Apache
  • Database design and admin (PostgreSQL preferred)
  • The use of PDO for database access
  • Web application security and best practices
  • Strong HTML, CSS and JavaScript skills
  • AJAX, implementation and debugging
  • Knowledge of Firebug and similar tools
  • Experience writing unit and regression tests
  • Selenium experience a strong plus
  • Perl skills a strong plus
  • Good Statistical mathematics a strong plus


Feature Development - Work with the product team to define feature specifications for the web-based components of our platform, and take a leading role in their implementation to production quality, complete with positive and negative test cases.

Testing - Testing is a primary focus in our development process, and every engineer is responsible for augmenting our automated test suite to guarantee test coverage on new and existing features.

Documentation - Ensuring documentation, code maintainability and product feature coherency.

This position is full-time in Columbia, MD.

We're only considering candidates with existing US work eligibility.

I'll be at ZendCon 2008

Busy times here mean that I'm leaving it a bit late to say this, but I'll be at ZendCon this year too. I'll be giving the usual talk on PDO, but my main reason for attending this year is to sync up with other PHP folks and talk about where PHP is at and where it's going.

ZendCon has been consistently good, and I look forward to attending again this year... see you there?

Slides: PHP Streams

Here are the slides from my Streams talk; they cover a variety of bits and pieces of streams background and implementation that may or may not be useful to you.

SlideShare | View

Slides: PHP and COM

This slide deck is from php|works 2004. There's a lot of material in the speaker notes, which I've painstakingly pasted into the comment on the slideshare representation (wouldn't it be cool if it could automatically do that?).

SlideShare | View

Just in case slideshare vanishes, the PowerPoint version is also available: PHP and COM

Slides: PDO

[I've just noticed that the re-design broke the various links from my blog to the slides I had been storing there. So I'm trying out slideshare; I'll be revisiting the slides I've given in the past and blogging one entry per presentation]

Here are the extended slides from my PDO talk. When I first put this talk together it was for a long hour slot, but conference sessions started to diminish in length and I had to pull out certain slides to avoid running over every time.

SlideShare | View

Just in case slideshare vanishes, the PDF version is also available: PDO