In this latest post to the Inviqa blog they ask the question "how clean is your code?" and offer a few tips to help it get that way (and stay that way).

During the Test Driven Development training (which includes Behat, and PHPspec) run by Marcello Duarte, I was particularly blown away by one of his many and funny analogies… “Would you have any surgery carried out by a doctor who does not wash his hands?” Everybody in the room shook their heads. Of course nobody would. There is too a high risk of complications. In software development ‘infected’ code can translate to bugs, bad user experience, poor performance and the complete failure of web applications.

He talks briefly about some of the lessons learned in this training session, pointing out that while it's not the easiest method to apply, it pays off in the long run of your code's "hygiene". He points out that the [Inviqa] group's success rate with TDD/BDD has reflected in the bottom line of their enterprise clients too.

On Dikiki.net today, there's a new post that's a continuation of a series (first post, second post) dealing with macro programming in PHP.

Without going into theoretical details, some of which are quite alien to me, I'll try to describe some of the challenges that pattern patching rewriting macros might pose for a language like php. After brief explanation what kind of a beast is this, I try to explore some of the finer points, which might cause problems. The intent of this post is to sketch a design and highlight some of the possible issues.

He breaks up the post into a few sections:

• pattern matching rewrite only macros - a bird eye view
• Transformation time
• Basic/skeleton shapes and intermediate shapes
• Code generation issues specific to php
• Hygiene
• A rough macro shape outline
• Output/Status of the project

There are code examples (of how it should work) and explainations of the issues PHP would face to accomplish this goal.

On Dikiki.net today, there's a new post that's a continuation of a series (first post, second post) dealing with macro programming in PHP.

Without going into theoretical details, some of which are quite alien to me, I'll try to describe some of the challenges that pattern patching rewriting macros might pose for a language like php. After brief explanation what kind of a beast is this, I try to explore some of the finer points, which might cause problems. The intent of this post is to sketch a design and highlight some of the possible issues.

He breaks up the post into a few sections:

• pattern matching rewrite only macros - a bird eye view
• Transformation time
• Basic/skeleton shapes and intermediate shapes
• Code generation issues specific to php
• Hygiene
• A rough macro shape outline
• Output/Status of the project

There are code examples (of how it should work) and explainations of the issues PHP would face to accomplish this goal.