What more can I say? php[architect] has done it again. It's clear that php[world] has made a place for itself in our community calendar, and I cannot wait for next year.
The slide deck for my workshop, Getting Started with Varnish, given on November 11th, 2014 at PHP World 2014
When we have a number of things to do with certain things needing to be done before others, how can we calculate the right order so that nothing gets done before it's ready to be done? The answer lies in graph theory and a very simple sort.
I got a wild bug last week to move my blog to a github page, so here it is. The volume of content that I produce certainly did not warrent a place even on the shared host it was living on. Plus, I’ve been meaning to play around with Jekyll for ages, and really, what better place than this? Please understand that some older posts will be somewhat discombobulated by the conversion process and it’s not likely that I’ll fix them anytime soon.
So, php[tek] has come and gone and everyone is hopefully starting to catch up on their sleep. This was my second visit to tek and while it was delightfully familiar, the conference had an entirely different energy compared to last year. From what I hear, this was the largest tek yet, and maybe it was the increased attendance that is responsible for the very different feel. During lunch breaks, the large central atrium at the venue was totally abuzz and each table was packed and lively with conversation. The atrium was pretty well packed, in fact, well in to the night with attendees talking and playing games. Not only was the conference well attended, but I understand that roughly half of the attendees were coming to tek for the very first time. In keeping with the conference’s Star Trek/SciFi theme, each attendee received a color-coded shirt: yellow for speakers (Captains in the chromatic language of the original Star Trek series), blue for repeat attendees, and red for first-timers. The venue was very, very well represented with red shirts!
I’ve been in the software engineering business for a long time, but until I was introduced to the PHP community, I never really cared to engage in the social aspect of this profession. I really feel that the PHP community is something unique. It’s rare to find a community that stands on the firm foundation of long-established friendships that is also so incredibly welcoming to newcomers.
"What on Earth is a Data Jam?" is precisely the question I asked myself yesterday afternoon when an email inviting me to participate in a White House Data Jam on STEM Workforce Quality, Flow, and Diversity landed in my inbox. Reading through some of the supplied documents made things only a little bit clearer. Despite the confusion and misgivings, I figured being asked if I want to come to a White House anything is a good enough reason to apply the Jim Halpert maxim and simply reply, "absolutely, I do."
SkiPHP has been a blast. The organizers have done a fantastic job putting together an amazing conference!
If you're interested in viewing the slides from my talks, they're available on speakerdeck, so please check them out!
No matter how popular an activity it is, I really don’t like to bash on PHP. Every language has its flaws when you look closely enough, and if PHP wears its idiosyncrasies a little closer to the surface than most, I think it makes up for it in other ways. PHP’s handling of types, however, is confusing at best and at worst completely deranged.
I’ve seen intercity rail schedules that can’t hold a candle to PHP’s type comparison tables. The bizarre and unexpected behaviors that can result from a non-strict comparison has all but rendered the equality operator (==) useless. The typical advice from PHP master to PHP neophyte is, always check for identicality (===) unless you’re very sure what you’re doing.