This post is written for SysAdmins, IT Directors, and CTOs who either manage a Drupal 7 site or are thinking of bringing a Drupal 7 site into their portfolio of technologies. My goal is to demystify Drupal and help you understand how it works, how to best manage it, and the various tools and techniques to help ensure a good experience with Drupal.
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.
I am preparing to release my blog, rjtownsend.com, as a Drupal distribution in the next week or so, "when it's ready" as is commonly said in the Drupal community. One of the pieces I was working on this last weekend was a demo-mode module that uses Drush to generate content during install. Here's how I did it.
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 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.
Today I was feeling a little delirious and decided to write a module that would embed a hidden easter egg on my site. After doing a little research, I decided that 1) The Konami Code would trigger the easter egg, and 2) Browser Ponies would be the hidden easter egg. Go ahead and try it out, enter the following code on your keyboard:
ssh into the server in question echo -e "flush_all\r\nquit" | nc `hostname -s` 11211
Three drupal devs walk into a bar. The first dev, an academic, said "I created the most elegant and bug free module ever today. I'm going to write and publish a paper on my novel abstraction layer!". The second dev, a consultant, said "I did not have full requirements and specifications for the module and now it’s throwing errors. I need more budget!”. The third dev, who happens to work in a marketing department, said "I have you all beat. My module resulted in a 150% increase in revenue. The module is perfect, I disabled error reporting!"