All Posts

Good testing will result in better code. If you have to wait endlessly for on SVN commits, uploads or compile steps, you will simply produce less inventive code. This has to do with: patience, creativity flow, will, and of course time. Constantly being interrupted breaks concentration. If there's one thing I've really learned, it's **invest in a good testing environment**. Rapid review of code results will pay off (I promise).

In another article I've told you about how I would like to see one rule removed from the PEAR Coding Standards. This rule would allow developers a bit more flexibility, while staying true to the convention.

Recently I've been experimenting with Virtual machines for my development environment. The goal was to create a Virtual Machine that resembles our main production server, and have that Virtual Machine mount my workspace project directory as its DocumentRoot. This way, my code could be served & tested after every save in my IDE. So no more building / committing delays. And all I could mess up was a Virtual Machine.

## Working With Trees When working with tree data structures you often need to craft them in different ways. PHP offers a lot of functions to change the shape of arrays, but often they only go 1 level deep. Trees can count an almost infinite number of levels. Hence we need recursive replacements for our beloved array functions.

## Working with trees When working with tree data structures you often need to craft them in different ways. PHP offers a lot of functions to change the shape of arrays, but often they only go 1 level deep. Trees can count an almost infinite number of levels. Hence we need recursive replacements for our beloved array & string functions.