"Why should we write our tests first? Isn't that going to slow my development?"
"What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!"
"Look, in the perfect world your advice is great, but I have a project to finish here."
In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
We recently wrapped up the first Ibuildings Challenge of 2012; a contest to create a Sismo notifier. At the moment Sismo ships with Growl, DBus, Google Talk and XMPP notifiers. They all extend the SismoNotifier to provide feedback to developers in a particular way. The task was to create a new notifier that was useful, creative or inspiring. This post announces the winners and makes some observations based on the submissions we received. (more...)
This is the second part of a series about Outside-in Behaviour Driven Development in PHP. The first part introduces outside-in development, and how to execute scenarios with Behat. Read this to catch up with the tools and the example we've used so far, then come back to find out how PHPSpec fits into this picture.
(more...)
Outside-in Development is an agile development methodology that places the intention and goals of the stakeholders at the centre of the process. This is achieved by having human-readable user stories and scenarios being invoked as scripts that feed back on the progress, continuously leading the development towards the stakeholders’ goal. Developers will start from this executable specification, and write the high level controllers that will provide the functionality. They then go into what they need to provide that functionality by specifying how their library class should work. By the time all classes’ specifications are met, all scenarios will also be fulfilled and the cycle is complete.
(more...)
19th - 20th September 2013
