I'm R.J. and this is my blog, it's a smattering of thoughts around technology, programming, open source software, the Drupal framework, and managing insane clients & projects. Thoughts are my own, read at your own risk, always safe-for-work.
Over the last 5 years I've interviewed more than 100 candidates for Drupal/PHP developer positions in everything from 15 minute phone screens to 4 hour on-site interviews that include technical exercises. In 10 minutes I can gauge a candidate's skills and experience as a Drupal developer and if s/he is a good fit for a position. In this post I discuss my philosophy and methodology around hiring a *good* Drupal developer.
SproutOnline.com has a variety of games and mobile apps that submit user-created data via POST to a URL and then email data to a gmail account. Not the most elegant way to do it but it's worked for years and they never had a problem. Last week something broke and we couldn't (quickly) find the cause. Instead of spending more time troubleshooting, I decided to create a resource in Services 3.x that would save each POST as a node. Read more to see how I did it.
I've been a part-time Linux sysadmin for a number of years and tonight I wanted to play around with Amazon EC2 and see how it works. There is plenty of documentation on how to configure and customize an Amazon EC2 instance and all the options available. However I didn't find a short, succinct summary of the steps required to spin up an EC2 instance from account creation to pointing your A record to it, so here goes.
I've found some fun Drupal modules that I wanted to share. These are low-maintainence, easy-to-setup background modules that will compliment most blogs and "fun" websites.
I'm sitting here waiting for a staging environment to build and I thought I'd reflect on the things I've learned from this client: