refactoring

Up until now, our application is simplistic as there is only one page. To spice things up a little bit, let's go crazy and add another page that says goodbye:

In a new post to his blog Marco Tabini offers some suggestions on unit testing - not really a tutorial on how to it, more of an "easy way in" to introducing it to your development process.

Richard Miller has a new post to his blog today that recommends moving away from the base controller the Symfony introductory documentation has you make.

He suggests an alternative that can be used more widely.

New on his blog today Lars Strojny has posted the first part of his look at dependency injection and how he's been using it to do some refactoring in his applications.

He uses the Symfony DI container in his examples, but really you can apply the principles to just about any of the other current DI offerings.

It’s a familiar situation: you’ve been developing on an application for hours and you feel like you’ve been going round in circles.

You fix one bug and another pops up. Sometimes, it’s the same one you found 30 minutes ago, and sometimes it’s new, but you just know it’s related.

For most developers, debugging means either clicking around on the site, or putting in a whole load of debugging statements to hunt the problem down.

When you look at the list of changes for PHPUnit 3.5, you will see that many of them deal with refactoring to components.

Here is an overview of these new components:

• PHP_CodeCoverage

  The collection, processing, and rendering of code coverage information has been factored out into a separate component.
  
  A bit more information can be found here.

To celebrate the 15th birthday of PHP, I have released PHPUnit 3.5 Beta 1 today. The refactoring towards components is a "new feature" that is already visible upon installation:

Francesco Fullone let us know that the Call for Papers for this year's Italian PHPDay event is now officially open!

Brandon Savage has posted a few suggestions about dealing with coding standards and how they can help improve the quality of your code via his refactoring of a bit of example code.

This time the focus is on documentation.

Revisiting an earlier post dealing with superglobals and classes, Brandon Savage looks at an example of why its still a bad idea.