September 10th, 2013
In my previous blog I explained how to handle the mythical "join tables with extra columns" in Doctrine 2. It comes down to _not_ creating a many-to-many association, but a one-to-many/many-to-one. But in the real world we usually treat this process a bit differently: We draw up a contract in which we specify the information that's needed, including the person and company it relates to.
September 3rd, 2013
This book is very accessible, with loads of examples and use-cases. It provides a good red line to follow, working from the lowest levels (estimating a story) to the highest levels (implementing for large distributed teams).
April 10th, 2013
Quite some time ago I read this article entitled "Cowboy coding and the pink sombrero". It's about editing code on the production server and how that's obviously a bad thing™
April 3rd, 2013
I've been building software for well over a decade now, and I'm absolutely guilty for breaking every rule below in the past.. but we've been adopting a more active approach to outlining our company beliefs, to live and breathe what we do every day. So here's our stance on password security: