Home / Implementing hook_career_alter()

Implementing hook_career_alter()

2011 has so far been a pretty amazing year, both for me personally, and also for the larger Drupal project. After nearly three years of hard work Drupal 7.0 was released, Lullabot sent me on tour to teach people about it, Drupal.org’s CVS => Git migration launched, and Drupal’s 10th birthday was celebrated at the amazing DrupalCon Chicago, where my mug was plastered on the cover of Linux Journal and Drupal 8 development officially kicked off. Whew!

So it’s with great excitement that I announce yet another huge milestone, both personally and Drupal-ly: I’m going to be making the move to Acquia, effective May 11, 2011. (Leaving enough time between jobs for a short vacation with my wife.)

Whoa! Who in the what now?

In my new role as Director in the office of the CTO, I’ll be focusing on maintenance and release management for Drupal 7, core patch reviews, coordinating with Drupal 8 development, evangelizing Drupal all around the world, and more.

It’s an amazing and exciting opportunity to help Drupal in an unprecedented way, working directly with Dries, at a company with a proven track record for major contributions to the Drupal project. I’m about to get paid full time to do what I love—making Drupal awesome—and couldn’t be more thrilled with the opportunity! :D

But what about the ‘bots?!

Unfortunately, this move also means I’ll be leaving the awesome team at Lullabot, with whom I’ve worked for nearly 5 years. Matt, Jeff, Liza, and the rest of the team have nurtured me on a journey from a wee PHP hacker to a consultant, trainer, book author, technical architect, and project manager. Lullabot has given me tremendous support over the years, and I’m eternally grateful to them for the opportunities and passions they’ve allowed me to pursue. Plus, they’re just some of the greatest people I’ve ever known.

Fortunately, I know the talented and passionate team at Lullabot will continue to do amazing things, and that we’ll all *still* be working together in the future. :)

So what happens now?

Basically, not much will be too different from before, other than I’ll be even more active in the issue queue, in various groups discussions, and on IRC, since it will be my job now. :) Dries and I will also be able to communicate and collaborate more closely than ever before, so expect things to pick up steam!

Community-related things that I’ll work on include maintaining Drupal 7, figuring out the Drupal 8 -> Drupal 7 backporting process, helping to create some communication and coordination around the Drupal 8 initiatives, and more.

I’ll be headed on-site at Acquia in mid-May to spend a few days with Dries hammering out the exact details, and then from there will fly to Minneapolis for a round of formal usability testing at University of Minnesota (please donate!), which should prove very informative for Drupal 8 usability priorities. Not bad for a first assignment! :)

As you can see, this is a truly amazing opportunity. I think being able to provide this sort of focused attention on Drupal itself will really help to increase our community’s progress and momentum. And I’m hugely looking forward to the opportunity to work full-time on what I’m most passionate about: Drupal.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.