Blog items

When I started working with Drupal (7), hooks were one of the concepts I appreciated. Although not 100% conceptually correct, for me, this hooking system is just a simplified way to react to events. Allowing to make changes/add functionality, by creating a function and sticking to a naming convention.

Automating repetitive tasks doesn't only give a satisfying feeling; it also prevents mistakes that you can easily overlook. Let's take setting up your development environment when working on a Drupal project, which is a process you ideally should do every time you start working on something else.

I'm using Windows for quite some time now, but honestly, it hasn't been the most comfortable operating system when you're creating software. Sure, there are workarounds, but the integration of development tools doesn't feel as smooth as on, for instance, Ubuntu.

When using automated tools to improve code quality, it sometimes happens that warnings are shown while the code is correct or hard to fix. Depending on your setup, this warning can prevent committing your code or setting up a test/acceptance environment.