Fixing problems when you see them and cleaning code as you go might cause you delays in the moment but can pay you back many times over in the future.

Software design patterns are an important part of every Software Engineers toolkit. This article is a short discussion of what it is, why it's important and where to find out more.

If you use a Boolean field with radio buttons in Drupal 7, the false radio button outputs before the true. This became an annoyance to us whilst working on mega-sized forms, so here's our fix. To fix this you'll need to create a custom module, and implement the hook hook_field_widget_form_alter(). The following code assumes your module is called 'example'. All the code does is reverse the order of the options whilst preserving the keys, simple!

Here is a handy tip for people using the variable module to get a list of all the possible types of variable the variable module supports.

You might find it desirable to place views template files into a module rather than the site theme. If the module is a feature which contains a view and is something that you might want to use on another site, then it makes sense to group the view and it's templates in the same module. The following article describes how to tell views that your module contains views template files and how to tell features that you want to tell views that the module contains views template files.

When you want even more control over an outputted field than display suite expert mode allows, you can put a theme function in template.php file. This article describes a neat design pattern for developers to use to experiment with a gives an example of how you might use it.

This is just a small post, but also a cautionary tale. From the moment you start working with Drupal and Javascript, you'll notice that the awesome jQuery library is thrown in for free. Not only that, but you've also got jQuery UI...