PHPNW 2014
3 - 5 Oct 2014 at Manchester Conference Centre

Thank you for this good talk about why BDD is so painful and opensourcing ShouldIT as a solution to run tests against written Acceptance Criteria.

Very nice and informative talk on naming variables/functions/classes etc. Very useful pointers and well delivered with a great sense of humor. Tx!

Very informative talk about all the new features in the latest PHP 5 versions. Nicely structured and very well delivered.

Very good talk, tackles the main reason why BDD isn't very well bought-in. Looking forward to having a peek on Should It on github.io

Less of a talk, more of a rallying call. It was good (if a little shameful) to see just how bad the WordPress / general PHP rift is.

A good talk with a realistic real-world example. No immediate jumping to design pattern refactoring.

Some slide composition would have helped to keep track of the topic. The Dependencies / Action / Response would have been clearer if it was all on screen at once, maybe as a flow chart. And side-by-side code comparisons would have had more of an impact instead of jumping back and forth.

The round up and the end was good, letting the audience know what to look at in the future to carry on.

Enjoyed this a lot, a different perspective. Having used Behat a lot before and discovered the Cucumber pain as a result, I was interested to see that others have had the same issues. The Markdown seems like a nice solution. Also enjoyed your presentation style. I would have liked to see some more detail on "real world" implementation and also on how it affected your takeup within the BBC and resultant test coverage, but overall very good - thanks!

Nice insight on some of the troubles BBC had with their tools. Although I still don't really know what "ShouldIt" does, this might be because I'm new to BDD.

I am not a security expert, I am a developer.

This talk did not give all information required to write secure web apps, but it did give information that everyone involved in writing a secure web app will need to know. Being familiar with this stuff is necessary for any web developer.

Nice to see someone who's talking about refactoring legacy to actually start from a really ancient example and gradually introducing modern practices. You should get rid of using the mysql extension though :) FYI: You have a very hangover-friendly way of taking :) Very nice talk!