Planet

Over the past week or two I've spent my time working on a Drupal install profile.

When it comes to commenting code there are two sides that often come up in discussion. On one side I'll regularly hear that code itself is readable so there is no need to comment it. And, typically code does speak for itself.

When it comes to commenting code there are two sides that often come up in discussion. On one side I'll regularly hear that code itself is readable so there is no need to comment it. And, typically code does speak for itself.

When it comes to commenting code there are two sides that often come up in discussion. On one side I'll regularly hear that code itself is readable so there is no need to comment it. And, typically code does speak for itself.

Here's a command that I find very useful when updating Drupal modules.

Ever had a (Drupal) website that just did not respond fast enough and you could not figure out what was causing it? I bet you did not look at the frontend code. The part which takes place in the browser of the site visitor.

Ever had a (Drupal) website that just did not respond fast enough and you could not figure out what was causing it? I bet you did not look at the frontend code. The part which takes place in the browser of the site visitor.

At the 2012 Bay Area Drupal Camp, I presented a session laying out a possible dev-test-live

Pages