Each year in December, we’re afforded an opportunity for contemplation of the past year as we look forward to the dawning of a new one in only a few days’ time. This look back at the year’s accomplishments was inspired largely by Laura Thomson’s declaration on Twitter that the Socorro team closed 1,000 bugs in 2012 – a truly amazing sum. I’m extremely proud of my team, and extremely proud of the work that we’re doing to make Firefox and the open web better.
I’m particularly proud of some of the things I’ve had the privilege to work on this year. Here are a few things that I worked on:
The following is an excerpt from a draft version of Do This, Not That: Object Oriented Development. Sign up today to be the first to get a copy this week!
A few weeks ago, I was tasked with integrating a library that was designed by someone else. This library was intended to access APIs and return the data so that it could be used by my application. This seemed straightforward enough, except that the API I was working with had a few quirks, namely that it interpreted the query string directly, and so it was possible to have a query string similar to this:
When I was a new PHP developer, I discovered that there’s a myriad of solutions, options, configurations and frameworks available. I thought, how does one sift through all the noise and get something done? How can anyone have a grasp of the best practices in PHP, and make sense out of all the options? Which extensions do we use, and how do we use them? What’s a best practice, anyway?
This is why I’ve decided to offer “Do This, Not That” for beginning and intermediate PHP developers looking to find a better grasp on precisely how to develop in PHP. This great series of highly focused e-books will offer tips, tricks and best practices focused on core areas of PHP development, including databases, security, filtering, regular expressions, configuration and more. Since it will be a series of tightly targeted solutions, developers will be able to pick all, some or just one of the offerings that solves their specific problem(s).
It’s been a little over a year and a half since I left the daily grind of a commute and began working from my home office. It’s been an amazing year filled with challenges, adventures, struggles and blessings. I’m like most developers: I relished the idea of having a quiet place to work, of getting more done, and of getting back 2 hours a day that I previously spent on commuting to and from my job.
I’ve learned a lot in my year of working from home. There have been some great moments, and some low ones. Overall it was a great move. So what is working from home really like?
Yesterday afternoon I used a random number generator to select three winners for The PHP Playbook.
I’m excited to announce that the winners of the PHP Playbook are:
- Péter Halász of the United Kingdom
- Ashar Javed of Germany
- Tomasz Kowalczyk of Poland
Another day, another article posted on Hacker News that describes PHP’s failures and complexities as though they actually mattered.
The truth is, only programmers care about languages. Only programmers care about the methods, routines, algorithms and organization of programming languages. Only programmers argue about coding styles, whether white space or brackets is the best way to separate code blocks, and about design patterns.