how-to

A few friends have asked me about my terminal setup, so I decided to write up a small blog post about it. This is what my terminal looks like in action: »

Using some kind of git branching strategy (e.g. GitFLow, GitHub Flow or other) normally produces quite a lot of branches. When these do not get merged on you »

I am by no means any photographer who generates thousands of pictures per year and has apps and workflows around all that, but a need to batch resize big pictures »

Many sites and distributions built on Drupal make use of Features. It often happens that having a big number of features on a site makes the Manage Features »

Drupal provides API for saving entities such as node_save() or user_save(). Functions like this update the whole provided entity, using up a lot of resources »

It happens too often that I get disconnected from a shell connection after a while of inactivity with message Write failed: Broken pipe. To prevent this, simply »

It can get really annoying when git status reports changes in files which are not really changed, just some file permissions have been modified. In most cases »

It usually is Internet Explorer that makes the life of a web developer hard, but this time I stumbled upon an issue when Mozilla Firefox added unexpected padding »