At work we use Omniture for our web analytics, and for a long time I've wanted query our Omniture Data to run some internal reports. I discovered that Omniture has a restful reporting api, and after using it for a little bit I decided it would be nice to write a wrapper library for it. Since I had recently taken the PHP Testing Bootcamp from Chris Hartjes, I decided I wanted write it using Test Driven Development and really get my feet wet. I also decided I wanted to make the library compatible with Composer. After the weekend was over, I had an almost finished library that just requires some more work to be done, but I learned a great deal that I thought I'd share.

He's broken the post up into sections, each with their own summary:

• TDD is 90% changing the way to write code, and 10% writing tests
• Understanding Mock Objects is the real key.
• It takes almost twice as long to write code and tests then just code
• Its extremely easy to get out of the habit of writing tests.
• You'll refactor quicker and more often when writing tests
• Having testable code made me feel much better about sharing the code.

After hearing about how great PHP Benelux Conferences were I finally made it over to Belgium to check it out, and i was impressed. To catch you up on the new, I moved to Amsterdam last december and thus had the chance of attending the conference which is now 2 hours away on a train ride. I could not expect less of a wonderful conference when names like Michelangelo van Dam are involved and this was no exception.

Among his suggestions, there's things like:

• Value your sponsors
• Value your attendees
• Make your attendees pay
• Value the organizers and your volunteers

...and one of the most important ones: "Have Fun!" If you're not following this piece of advice, you're probably doing it wrong.